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

ui-ota: the publish order rule in the plan (1.0.1 with min_engine 0.3.20 only after 0.3.20 is on the manifest)

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
(cherry picked from commit ee09ae8b633206c8a7ab438eb4b0ee57362de000)
This commit is contained in:
igneum-labs 2026-10-07 10:35:39 +00:00
parent 272b542120
commit bb3649a266
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/plans/ui-ota.md
View file

@ -83,6 +83,10 @@ node tools/ui-ota/publish.mjs --version 1.0.1 --min-engine 0.3.20 --notes "one l
node tools/ui-ota/publish.mjs --verify
```
Order rule (the shipper, 7 October 2026): the 0.3.19 app, live since 10:23Z, ignores the `ui` object, so 1.0.1
publishes with min_engine 0.3.20 only after 0.3.20 is on the manifest; an earlier publish is harmless (every 0.3.19
engine skips it) and pointless. The kill switch (`--no-ui`) sits in the shipper's runbook beside the manifest's own.
What it does: writes ui/VERSION from --version, packs the fifteen served files in sorted order with one fixed mtime
(the same tree gives the same bytes; the self-test checks it), hashes, signs the entry through
`igneum-ota-sign sign-ui`, copies the tar into the folder's ui/, writes ui.json and calls