igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

release-0.3.6 plan: the ship, the live manifest compared field by field

Browse source
This commit is contained in:
igneum-labs 2026-10-05 09:35:31 +00:00
parent ed669e7024
commit 257704a83f
1 changed files with 50 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

50
docs/plans/release-0.3.6.md
View file

@ -436,3 +436,53 @@ The digest equals the live one (difficulty 33000, proving 84100); the fee switch
| windows | inno-setup 0184abec..., 44,447,899 |
`publish-manifest.sh` carries `consensus.override` and `tuning` over from the folder's manifest when not given; `activation_height` and `deadline_note` only come from flags, so the ship command passes `--activation-height 84100 --deadline-note "proving v0"` to keep the consensus object identical field by field.
### 8i. The ship
The push: the project lead pushed `release-0.3.6` at 5483322 (09:29Z). `windows.yml` runs only on master pushes, so the run was
dispatched on the branch: `gh workflow run windows.yml --ref release-0.3.6` → run 37290313983, started 09:29:00Z,
green 09:33:40Z (both jobs: the PowerShell and batch parse checks; engine, window host, payload, installer, smoke
run; the G13 inputs step verified the signed payload inputs of 8f against the pin).
Preflight refused the real run on one count, "10 commits behind origin/master" (master had moved to 2766b26: site
pages, litepaper v0.2, the PCs build rule, the packer stamp), so origin/master was merged into the branch (8a79f35)
as the coordinator allowed: `site/build.mjs` takes master's PRODUCT table and PAGES; master's `/wallet` is the
product page and the testnet-prep MetaMask page moved to `/metamask` (in PAGES and the sitemap, the two links on the
home page retargeted); the testnet terms card stays on the home page under master's miner section; litepaper takes
master's Ember wording; `node site/build.mjs` then `node tools/ci/link-check.mjs`: 475 links across 10 pages, 0
broken. Those commits touch no app or packaging file, so the installer built at 5483322 is the release; the ship
state file (`~/.cache/igneum/ship/0.3.6.json`) got `sha` = 5483322, what the tool's own commit step would have
recorded, and the run resumed with `--from ci`.
```
node tools/ship-app.mjs 0.3.6 --node vendor/igneum-node-036 --branch release-0.3.6 --dl-both \
--activation-height 84100 --deadline-note "proving v0" --notes "Instant jobs, a proof verifier for the node, one notice strip, lower miner latency, packaged configuration, hidden helper windows; node 2b6d23ef: testnet identity and the fee table behind a height switch, signed build inputs" \
--from ci
```
| Step | Result | Time |
|---|---|---|
| preflight | ok (tree 8a79f35 clean, 0.3.6 in all 6, fork 2b6d23ef, both exes, both Mac binaries, both folders, gh igneum-labs, live inputs 2b6d23ef) | 09:31:48Z |
| ci | green after 2 min of polling | 09:34Z |
| fetch | Igneum-Miner-Setup-0.3.6.exe 18.6 MB, igneum-windows-app.zip 26.0 MB (`OTA_SKIP=1 CONSOLE_SKIP=1 fetch-ci-artifacts.sh 37290313983`) | |
| dmg | already (8h2) | |
| copy | the DMG into the OLD folder | |
| mirror | 10 files into the NEXT folder, sha256-checked | |
| manifest | `consensus.override` carried over from the folder's 0.3.5 manifest; both manifests signed (key 8f186e37...), verified locally, same fields | |
| deploy | one deploy of the downloads folder | 09:34Z |
The live manifests, read 09:35:00Z, compared field by field with the 0.3.5 record of 8h:
| Field | OLD folder | NEXT folder |
|---|---|---|
| version, channel, min_supported_version | 0.3.6, devnet, 0.3.0 | same |
| published_at | 2026-10-05T09:34:06Z | 2026-10-05T09:34:07Z |
| consensus | identical to the live 0.3.5 object: override {difficulty_v2_activation_daa 33000, proving_v0_activation_daa 84100}, activation_height 84100, deadline_note "proving v0" | identical |
| fees_v1_activation_daa | absent | absent |
| tuning | absent | absent |
| mac | dmg fddf3580353d87e0b4f9a910894c507eb5b1cab7b500f4cb9d653db34a7af311, 40,156,607, URL in its own folder | same bytes, URL in the NEXT folder |
| windows | inno-setup ca0fb9197bee6e3a867a33f4e6bcd2c570c9136444e3587ac311d23bfde61531, 19,536,899, URL in its own folder | same bytes, URL in the NEXT folder |
`igneum-windows-app.zip` cf91659a64afceb0fb4cdb29e7691b5057f1ec264d6fd6d07cd725b23e2cdddc. The 0.3.6 installer is
19.5 MB against 0.3.5's 44.4 MB: the payload no longer carries what the PC builds itself (to confirm from the CI
payload listing; noted, not verified here).