Skip to content

G1 Install and update: Signed update #89

Open
6 of 8 issues completed
Open

Description

@andersalm

Release: 0.8.0.

First goal (2 Oct, done): signed install and update on a Mac; history in comments.

Owner: Anders (@andersalm).

A Home owner can see a later signed release in System, approve staging, and restart when ready. Runtime stages a complete release beside the current one. If the new version cannot start, the supported recovery path restores the previous complete release. Identity and user data stay intact.

Done means

Review rule (Anders, 10 Oct): for install/update, independent reviews by other models (cross-family review, devil's advocate, Grok) replace the pending human reviews, and OMP's own Mac, Linux and Jetson runs replace Sasha's repetition.

Release acceptance: Each exposed feature works clearly from start to end, including recovery. Keep unfinished or confusing features hidden until their complete journey passes. Hiding a feature does not complete its task; source checks alone do not establish installed acceptance.

Tasks: UP-00 (#106) through UP-07 (#113) under this issue. System is the first entry point. Marketplace shows the same Runtime update state later (#111, moved after local AI and Browser on 5 October).

  • When a release brings a component kind the Home's version does not know, Update still works (the new version installs it at start). If an update cannot be applied at all, System and elastos update show the install command instead of 'the publisher's signed release is not valid'. Test: CI's update journey from alpha.15 to the candidate passes, and a test release with an unknown component kind either installs or shows the install command.

Remaining for 0.8.0

Single list for install/update; #88, #93, #113 and #311 link here.

Known gaps users can see, not in 0.8.0 (milestone After 0.8.0): #297 (Undo needs the previous head CID saved by hand) and #305 (Update or Undo before setup says the install needs repair).

Browser

Browser update and repair requirements (B15) are part of the Browser goal: #283 and #87.

Clean-up (PR #358, after alpha.16)

Activity

  1. added this to the 0.7.1 milestone on Sep 29, 2026
  2. self-assigned this
    on Sep 29, 2026
  3. andersalm commented on Sep 29, 2026

    @andersalm
    ContributorAuthor

    QA retest 2026-09-29 (published install vs release-head)

    Verdict: STILL_REPRO — channel/version drift between published binary, update plan, and marketing.

    Steps

    1. On Linux x86_64: inspect /home/box/.local/bin/elastos from the public installer path.
    2. Run under clean env: elastos --version, elastos update --check / upgrade --check.
    3. Fetch https://elastos.elacitylabs.com/release-head.json and the marketing landing /.

    Expected

    Published install identity, update plan, and website messaging agree on what a new user should install and what update means (Done means for signed update / install).

    Actual

    Signal Value
    Binary elastos 0.1.2 · sha256 f6da8ce7db012fba4e8443fce372e0f8a8e6bdf4df1e84e50272396cfb87eba8
    update / upgrade --check plans 0.1.2 → 0.7.1
    release-head.json payload.version 0.7.1 (updated_at 2026-09-18)
    Landing still “0.7.1 installer coming soon.” with Copy disabled / Coming soon

    Evidence

    /workspace/elastos-qa/github-reset-20260929/retest-public/ — RETEST.md, qa47-cli.txt, release-head.json, landing screenshot if present.

    Also related to #88. Notion archive id: QA-47.

  4. andersalm commented on Sep 30, 2026

    @andersalm
    ContributorAuthor

    Paused on 30 Sep at 15:40 UTC (Codex weekly limit). State for the next thread:

  5. changed the title [-]0.7.1: Signed update[/-] [+]0.8.0: Signed update[/+] on Sep 30, 2026
  6. andersalm commented on Oct 1, 2026

    @andersalm
    ContributorAuthor

    QA Deployment 2026-10-01 (~08:49 America/Bogota) — WORSENED vs 2026-09-30

    Published binary identity unchanged (elastos 0.1.2, sha256 f6da8ce7…eba8). New: update --check / upgrade --check fail with Carrier connect timeout, and https://elastos.elacitylabs.com/release-head.json (plus / and /home/) return HTTP 502.

    Filed: #162. Local published Home smoke on 127.0.0.1:61201 still HTTP 200.

    Evidence: /workspace/elastos-qa-deploy-20261001-0848/.

  7. andersalm commented on Oct 2, 2026

    @andersalm
    ContributorAuthor

    The update session is now in progress for M1/M2 on approved develop 829a24ad7ed3617eb3a48083e0b5cda627b8b9e9; #156 carries the client work. Local AI PR153/136/148/208 and broader PR151/161 are parked as drafts with published state and resume notes; today’s Jetson outcome and Sasha’s Codex reviews are complete.
    Fixture contract for agreement: two ordered Mac versions on one supported test channel, signed head/release envelopes under the new maintainer DID, exact source/tree/binary/component/installer hashes and valid Carrier content CIDs. Existing publisher_dids pins the signer; publisher_node_id / connect_ticket select the separately owned Carrier holder, so source schema stays unchanged.
    The release session supplies the signed public fixture, installer and completed publication/content receipts. Carrier CID delivery needs the qualified IPFS provider/Kubo content, beyond copied Publisher JSON. Signing custody and all seed, publish and real-Mac install steps stay with the approved operator.
    The update session first verifies the staged executable before live replacement and adds refused signer/hash/platform/version cases. The CI integration will extend existing scripts/update-hop-compare.py and scripts/update-hop-compare-test.py, called by the macOS CI job, for install → plain Carrier check/apply → preserved config/data → repeated up-to-date result.
    Please record the fixture’s stable input/receipt reference and the minimum shared install-lock/commit boundary here before either session changes that contract. M1/M2 use the fresh CLI installation; wider complete-set and running-Home restart acceptance remain in #108/#109.

  8. 165 remaining items

  9. andersalm commented on Oct 16, 2026

    @andersalm
    ContributorAuthor

    alpha.19 Linux System update 18->19 (UI): after the restart the managed Home runtime is not started until the page reloads, so Community posts do not arrive and the header says "Community unreachable" (sending still works). Cause: only the page boot calls /api/apps/home/runtime/ensure (home-shell-host.js:2343-2350); with ELASTOS_UPDATE_RESTART=1 the gateway opens no page (gateway_entry.rs:33-36). Workaround: reload Home after an update. Fix for 0.8.1: the gateway ensures the runtime itself on an update restart (gateway_entry.rs); it runs in the new version, so it also covers 0.8.0 -> 0.8.1. Non-blocking for 0.8.0: stable users install 0.8.0 with the install command (fresh page boot).

  10. andersalm commented on Oct 16, 2026

    @andersalm
    ContributorAuthor

    Installed alpha.19 Linux x86: System update 18->19 twice: step texts in order (queued, checking, downloading 109.4 MB, verifying, restarting, up to date), restart 12-20 s, model/chat/draft kept, offline reply 2.4 s; Undo (rollback-to alpha.18) 203 s with data kept; arm64 fresh install + Kit restore same DID. PASS. Non-blocking (0.8.1): the "You cancelled the update" text is replaced within 16 ms; Undo/terminal update leave Home stopped without saying so; elastos source show prints "Head CID: unknown".

  11. andersalm commented on Oct 16, 2026

    @andersalm
    ContributorAuthor

    Mac System update alpha.17 -> alpha.19 (Anders's Home): request 19:25, verifying 19:27, restarting 19:28:23, "Home is up to date" 19:29:43 COT; installed binary 0.8.0-alpha.19, Home 200. alpha.17's System showed "Home has not completed the update. Open System from Home again" while the controller was still verifying: the old screen stops waiting early; alpha.18 and later poll through the restart (e5d054b). PASS.

  12. andersalm commented on Oct 16, 2026

    @andersalm
    ContributorAuthor

    Remaining for 0.8.0 (15 Oct 22:45 COT; final candidate alpha.21 = alpha.20 + automatic Community recovery; plan #93 6207232773): alpha.20 -> alpha.21 System update + Undo on Mac, Linux, Jetson (installed). Owner decision: the alpha.14 Mac reinstall box: run it or move it to After 0.8.0. Unknown-component box: source proof only (update.rs installer_required test). Advisory GHSA-wgx8 publishes with 0.8.0 (#311).

  13. andersalm commented on Oct 16, 2026

    @andersalm
    ContributorAuthor

    Status list updated: #110 is closed with proof; #338 is closed and #335's code shipped (stable mode in release-publish.sh), so those two "remaining" lines are ticked. The cross-version box stays open only for the alpha.14-or-older path (owner: run or move); alpha.15+ System updates are proven on Mac, Linux and Jetson (this issue, 15-16 Oct).

  14. andersalm commented on Oct 16, 2026

    @andersalm
    ContributorAuthor

    Installed alpha.21 (Linux, 16 Oct): System update alpha.20 -> alpha.21 in the UI twice: step texts in order (passkey, checking, queued, downloading 109.6 MB, verifying, "Restarting to finish the update. Home is usually back within two minutes.", "Home is up to date." at 103 s / 72 s), Home back ~19 s after restart, model, chat and draft kept; offline reply 1.26 s; Undo to alpha.20 in 18 s with data kept; fresh installs x86 and ARM, ARM lock -> passkey sign-in. PASS. These paths are untouched by the alpha.22 Community fixes, so they carry. Evidence a21-linux-20261016T1220Z.

  15. andersalm commented on Oct 16, 2026

    @andersalm
    ContributorAuthor

    Installed update checks on 0.8.0-alpha.22 (OMP, 16 Oct, run a22-update-20261016T1825Z; raw logs in the private evidence store). Candidate: alpha.22, source f346147, head QmXnA5ao7PMfwdj7pGaxpWs14gfgD15FtmhVQPj1EphFXm (#93 comment 6221170970).

    • Linux x86-64, System update alpha.21 → alpha.22: PASS in 141 s (passkey, queued, checking, download 109.6 MB, verify, "Restarting to finish the update. Home is usually back within two minutes.", same page, no reload). Selected model, chats and own Community post kept; Community live with posts both ways after the restart.
    • Undo in Terminal (alpha.22 → alpha.21): PASS, rc 0 in 55 s; afterwards own posts kept (2), model picker still "SmolLM2 135M Instruct", Assistant reply in 1.6 s.
    • Update again in Terminal (elastos update, alpha.21 → alpha.22): PASS, rc 0 in 51 s, Home 200 after 15 s; elastos home --browser brings Community back.
    • Linux arm64, System update alpha.21 → alpha.22: PASS in 124 s (download 100.4 MB, same restart text). A first attempt timed out on a test-script click of Send, not on the update.
      Not covered by this run: an offline (network-off) reply, an unsent draft, and the Mac (Anders's Mac and Jetson Homes run alpha.22).
  16. andersalm commented on Oct 16, 2026

    @andersalm
    ContributorAuthor

    Milestone sweep (16 Oct, alpha.22 = final candidate):

  17. andersalm commented on Oct 16, 2026

    @andersalm
    ContributorAuthor

    Body updated (16 Oct, 0.8.0 scope rule): alpha.14 Mac reinstall box struck → After 0.8.0 (affects alpha.14 testers only, not new users; reversible). The Jetson fresh install in #88 stays as a post-publication install step. Remaining list reconciled: #156/#314 closed; #317/#319/#320/#321/#183/#274/#363 are After 0.8.0; #88 Recovery Kit item already ticked there. Unchanged: unknown-component-kind update box, #113 runs, advisory.

  18. andersalm commented on Oct 21, 2026

    @andersalm
    ContributorAuthor

    OMP has prepared the unknown-component CLI and System test cases at 0a4cde4c2. The System test delta passed sys1 source review; kind2 delta review at 992f71c67 closes the earlier CLI snapshot finding. These reviews cover test source and validator checks.
    OMP reports that the first rehearsal stopped at its pre-start port check at 18:34:31 UTC and run4 ended during its port wait after setup. Neither reached the unknown-component case; run4's exit cause remains unknown. After Anders's Home-stop handoff, OMP reports run5 passed its local rehearsal at 0a4cde4c2, using disposable signed fixtures, from 11:18:17 to 11:23:27 UTC on 22 October. The report records CLI and System handling of an unknown component as installer-required, data preservation at that refusal, five CLI refusal cases on each path and System refusal of a tampered binary. OMP told Anders at 11:24 UTC that the rehearsal ended and his own Home could restart. At 11:40 UTC Anders confirms Home is up and seems to work well. Earlier attempts and their methods remain in the record.
    This is an owner-reported local fixture result on earlier source. OMP integrated the three #89 commits as dc702755a, 4023ef12a and ba224ca2b, after the two F3 follow-ups. Their named reviewed changes are preserved, including the train's earlier System reload guidance. The configured Linux source gate on ba224ca2b failed in 3m37s in the Home reload test. The configured Linux source gate at 9382cd50e passed in 24m16s. New test-only commit a6b52a808 applies the remaining predicate correction from reloadsmoke2's PASS WITH CHANGES. OMP reports text-level compatibility with #435; the current train's two update-hop receipts, installed Runtime/System journey and exact candidate CI remain open. Changes to the train's update smoke need qualification on that combined head. #113 keeps its approved post-publication order.

  19. andersalm commented on Oct 22, 2026

    @andersalm
    ContributorAuthor

    The 22 October audit rechecked the Normal CLI rollback boundary on candidate 460b1888d and recorded the still-present complete-support recovery gap in #108. Treat it as release triage before relying on #108's closed state. The required failure is after one changed support asset succeeds, not during the initial binary download. This is separate from #297's accepted offline-Undo deferral. No installed reproduction or source change was made.

  20. andersalm commented on Oct 29, 2026

    @andersalm
    ContributorAuthor

    The holder canary needs a fixture update before it runs again on the 0.8.0 train.

    On the 0.8.0-alpha.26 candidate (5f65bee37 and later), a Home serves a peer only the content of its active Library shares, and it serves the raw CID routes over HTTP only to its own sessions. A node that serves publisher content, such as the seed, keeps serving everything it holds. The fix is the one the installed journeys use (serve_as_seed in scripts/ci-installed-journeys.py, commit 57627f88c): create ElastOS/SystemServices/Publisher/artifacts in the node's data directory before it starts, so it acts as a publisher node, as the seed does. The Rust holder tests do the same.

    • scripts/holder-idle-ci.py (the always-on holder): fixed on the train in 57627f88c.
    • .github/workflows/canary-holder-linux.yml:346-391: open. Both inline roles need the marker: the holder for its Carrier read, and the gateway for its anonymous /content/:cid read (Codex review ci1 on 57627f88c).

    This canary runs only on a pull request that touches its paths, or on manual dispatch. It is not part of develop CI or the package run, so it does not block alpha.26. It must pass before the release pull request to main.

  21. andersalm commented on Oct 29, 2026

    @andersalm
    ContributorAuthor

    Holder canary on the 0.8.0 release source: run 40954703350 success, on branch ci/080-holder-canary-a26 = 8a74b669c (the signed 0.8.0-alpha.26 source) + e22d14a6e, which changes only .github/workflows/canary-holder-linux.yml: the holder and gateway roles get the seed marker (ElastOS/SystemServices/Publisher/artifacts) before they start; the consumer stays an ordinary Home. The fixture commit lands on develop after 0.8.0 so the release stays the signed commit. Note: this workflow has been disabled_manually since 6 Oct 11:06 UTC with no recorded reason, so it does not run on pull requests; it was enabled for this one dispatch and disabled again. Whether it should stay disabled is open.

  22. andersalm commented on Oct 30, 2026

    @andersalm
    ContributorAuthor

    The previous-release CI fixture now selects its signed optional providers explicitly, while the ordinary Home profile stays unchanged. This addresses the setup mismatch in run41098962840.
    The new omission case failed before the repair; all four install-fixture tests now pass, including signed-hash tamper refusal. Independent review passed on the local correction.
    The correction is prepared under PR375; the new candidate still needs the normal push gate and actual installed update/Undo proof.

  23. removed this from the 0.8.0 milestone on Nov 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions