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

release-0.3.9 plan: the cut so far (branch, tests, node builds, hand nodes and seed on a24ab01a, DMG, package)

Browse source
This commit is contained in:
igneum-josh 2026-10-05 17:51:20 +01:00
parent ea08798ffd
commit f2d618c5e4
1 changed files with 9 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/plans/release-0.3.9.md
View file

@ -34,7 +34,9 @@ and the hand nodes and the seed export nothing), and the node's `kaspa-rpc-servi
| f7a41a2 | Merge `fee-switch` (15bb6cd, landed 16:24Z). Conflicts: `proving/igneum-prove/export/src/main.rs` (only the two `use` lines: master's `ensure` kept, fee-switch's `FeeParams`, `FeeSchedule` taken, `SHARD_PROVING_GAS_BUDGET` gone), `docs/bench-log.md` (both entries), `docs/testnet/README.md` (both sentences), `site/index.html` and `site/journey.json` (master's, then `node site/build.mjs`: 13 pages, `link-check` 518 links, 0 broken) |
| 2b6bf7f | `Igneum Miner 0.3.9: ...`, the six version files (`node tools/ship-app.mjs --check`: 0.3.9 in all 6) |
| dfc0cfc | `packaging/windows/node-source.pin` = a24ab01a (written by `push-inputs.sh`, section 5b) |
| 00c7b4f | `infra/devnet/restart-hand-nodes.sh` and `restart-seed.sh` take the fork tip's commit and the seed's cross-built binary by variable (section 5c); pushed 16:42Z, `windows.yml` dispatched again on it: run 37342911129 |
| 00c7b4f | `infra/devnet/restart-hand-nodes.sh` and `restart-seed.sh` take the fork tip's commit and the seed's cross-built binary by variable (section 5c); pushed 16:42Z, `windows.yml` dispatched again on it: run 37342911129, green 16:48:10Z. THE RELEASE COMMIT for the installer (every later commit is docs and site) |
| 97b1a74 | `origin/master` fb076de merged (12 more commits: fud-a round 6, the Igneum Labs LTD imprint, `tools/ci/no-conflict-markers.sh` with a pre-push hook that rebuilds the site; among the build inputs only `.github/workflows/ci.yml`). `docs/bench-log.md` both entries; the site taken from master and rebuilt (519 links, 0 broken, no markers) |
| (next) | `site: rebuilt on this tree`: the pre-push hook's build of `site/index.html` and `site/journey.json` differed from master's copy (two journey entries' wording), which left the tree dirty and the ship's first run (16:48:47Z) stopped in preflight; the generator's own output committed |
| 1269db8 | `origin/master` 318a2de merged (coordinator 16:32Z: housekeeping, the signed jobs envelope `igneum-jobs.signed.json` on both sides, `test-publish-jobs.sh`, `ship-app.mjs` carries the envelope in FOLDER_FILES and `--public`); it rewrites four app sources (`jobs.rs`, `jobrun.rs`, `jobbuild.rs`, `bin/ota-sign.rs`), so the chained build that had started at 16:31Z was killed at its app step and restarted from this tree, and the app tests rerun. The fork's own `housekeeping` branch is NOT in 0.3.9 (0.3.10) |
## 3. Tests and checks, with the command
@ -194,7 +196,12 @@ through the MAIN checkout's `publish-jobs.sh` (coordinator's rule, 16:31Z: that
the main checkout's `app/igneum-app/target/release/igneum-ota-sign` was built 07:38Z, before the `sign-jobs` subcommand
existed (the script printed the signer's usage). The signer built from this tree (the chained build's app step, which
carries `bin/ota-sign.rs` with `sign-jobs`) is copied over it, then `publish-jobs.sh sign --deploy` publishes the file
with the job and a fresh envelope: the signer from this tree (595,024 bytes, built 16:41Z, `sign-jobs` present) copied
with the job and a fresh envelope. BUT: the failed `add` had not written the job (the file is replaced only after it
is signed), so the 16:42Z `sign --deploy` re-published the file WITHOUT `fetch-prove-039`, PC 2 had nothing to fetch, and
the 16:46:04Z live file (84 jobs, another agent's build job) confirmed the absence at 16:48Z. The job was added again
at 16:49:20Z through the main script with the new signer (`added: fetch-prove-039 ... until 2026-10-06T04:49:21Z`,
envelope and pair verified, apps woken, stamp f45d504a); PC 2 was then busy with another agent's build job
(`build-20261005-164604`, started 16:48Z), one job at a time, so the fetch queues behind it. The signer step: the signer from this tree (595,024 bytes, built 16:41Z, `sign-jobs` present) copied
over the main checkout's (the 07:38Z one kept as `igneum-ota-sign.pre-envelope`), `publish-jobs.sh sign --deploy`
16:42:13Z: `live jobs files verified at .../igneum-jobs.signed.json and the plain pair (try 1 of 12)`, apps woken (stamp
2026-10-05T16:42:14Z.9e4b22bb). Lesson for the class: a script that needs a newer signer than the checkout has built