Repository navigation
Description
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.
- Runtime validates version order, source, channel and fetched content. Explicit Undo is distinct from an accidental downgrade. (Plain downgrade refused and Undo distinct in the CI journey, PR ci: update from the real published alpha.6 to each PR build, then Undo with --rollback-to (#89, #109) #259/Next train after alpha.8: one update planner, one file lock, #279, #280, flaky tests, CI journey from alpha.8 #284; real channel refusal G1 Install and update: Signed update #89 (comment); real content refusal #109.) Proof: G1 Install and update: Signed update #89 (comment)
- Staging covers Runtime, components, engines and capsules (models are published separately, release: take the four AI models out of the release #236); the running Home keeps its current set until restart. (PR update: stage the complete release while Home runs, then stop once (#108, #110) #246; real System update alpha.7 → alpha.8 changed 19 components while Home kept running G1 Install and update: Signed update #89 (comment).) Proof: G1 Install and update: Signed update #89 (comment)
- One installation lock and layout cover fresh install, legacy upgrade, custom paths and installer reruns. Proof: UP-07: Accept updates on Mac, Linux and Jetson #113 (comment)
- Restart, readiness failure and Undo preserve user data, including data written after the update. (evidence: UP-07: Accept updates on Mac, Linux and Jetson #113 (comment), UP-03: Restart and recover safely #109 (comment)) Proof: UP-07: Accept updates on Mac, Linux and Jetson #113 (comment)
- System exposes the shared updater state and binds approval to the exact release. (Exact-intent and fresh-passkey tests in gateway_home_update; real run G1 Install and update: Signed update #89 (comment).) Proof: G1 Install and update: Signed update #89 (comment)
- Real signed updates pass on Mac, isolated Linux x86-64 and Jetson. (Re-trusting old-key installs by re-running install.sh happens on the stable channel and is a 0.8.0: Release 0.8.0 #93 release gate; canary refuses a stable-channel install by design, comment 6027044808.) Proof: UP-07: Accept updates on Mac, Linux and Jetson #113 (comment)
- alpha.6 first hop: existing users move off alpha.6 through
elastos updatein Terminal or install.sh, because alpha.6's System refuses changed support (comment 6021378752). (G1 Install and update: Signed update #89 (comment); CI journey PR ci: update from the real published alpha.6 to each PR build, then Undo with --rollback-to (#89, #109) #259.) Proof: G1 Install and update: Signed update #89 (comment) - System update from alpha.7 to a release with changed support passes in Home. (Anders, Mac, 7 Oct: G1 Install and update: Signed update #89 (comment).) Proof: G1 Install and update: Signed update #89 (comment)
- Refusal, interruption, restart and Undo each pass on the installed update. (evidence: UP-07: Accept updates on Mac, Linux and Jetson #113 (comment), UP-02: Stage one complete release #108 (comment)) Proof: UP-07: Accept updates on Mac, Linux and Jetson #113 (comment)
- Cross-version: Homes on alpha.15 or later update in System. Proof: alpha.21 → alpha.22 System update on Linux x86-64 and arm64 G1 Install and update: Signed update #89 (comment); Anders's Mac and Jetson Homes updated alpha.21 → alpha.22 Community: presence replay records fill the 4,096 incoming table and stop intake #401 (comment)
Homes on alpha.14 or older re-run the install command once (their System refuses safely; data kept). Test: on a Mac on alpha.14, re-run the install command and check the DID, passkey and Chat are kept.→ moved to After 0.8.0 (16 Oct): affects alpha.14 testers only, not new users. The Jetson fresh install in G1 Install and update: Install, sign in and recover #88 stays as a post-publication install step.- Homes that imported media tools before alpha.9 finish setup with no manual step (fixed in alpha.15). Proof: https://github.com/Elacity/elastos-runtime/blob/aa3d61e4478a1a1a63dbef0dae97c23a0f9f4851/elastos/CHANGELOG.md#L45 (fix a1a7968 in PR 0.8.0-alpha.15: install/update closure, Local AI fixes, Browser on Mac and Jetson #343) Test: on Anders's Mac, re-run the install command over alpha.14; setup finishes without moving protected-content/media-provider.
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 updateshow 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.
- UP-07: Accept updates on Mac, Linux and Jetson #113: immediately after stable publication, prove the available 0.8.0 update fails plainly on an offline Jetson and leaves its Home unchanged; reconnect and apply that same update. Approved target and order. Online update runs already pass; UP-07: Accept updates on Mac, Linux and Jetson #113 owns the remaining proof.
- UP-04: Add the System update flow #110: one check left (clear messages on a real update); see its Test.
- Recover invalid installed versions and admit update manifests before replacement #156, Release fetches use HTTPS only, with loopback HTTP for fixtures #314 closed;
Required checks run whenever their inputs change (path filters) #317, CI proves install and update on Linux #320, A documented procedure to withdraw a bad release #321→ moved to After 0.8.0 (milestone set there). The local pre-push gate refuses what CI refuses #319 (pre-push gate)→ moved to After 0.8.0.- G1 Install and update: Install, sign in and recover #88: Recovery Kit restore on a second machine is ticked there;
session list and revoke→ 0.8.1: List and revoke your own sessions, with a maximum sign-in age #363, After 0.8.0. Installer: run the Runtime as a limited service on Linux and macOS #183 and update: every capsule signed independently; updates replace only changed capsules #274 with Installer: clear steps, ElastOS banner and plain output for pipes #252/feat(setup): one progress line per component with signed sizes #277→ moved to After 0.8.0 (milestone set there).- No code yet: 0.8.0 publication: sign one release for both stable and canary #335 (one release for both channels, a 0.8.0: Release 0.8.0 #93 gate) and Account: lock screen shows no errors, and an owner cannot add a second passkey #338 (sign-in errors and adding a passkey, part of G1 Install and update: Install, sign in and recover #88).
- Advisory GHSA-wgx8-qf6g-cj4h publication: owned by Install, update, release and CI remediation (9 October review) #311.
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)
Delete dead update code:→ moved to After 0.8.0 (PR Cleanup for 0.8.0: dead update code, unused providers, IPNS plumbing, one copy of install and isolation text (#89) #358)run_update,run_frozen_update_for_data_dir(update.rs) and the CHANGELOG text about the frozen offline path; rename upgrade/p2p leftovers (run_upgrade_with_restart,TryP2pFn)Delete unused→ moved to After 0.8.0 (PR Cleanup for 0.8.0: dead update code, unused providers, IPNS plumbing, one copy of install and isolation text (#89) #358)IpfsStreamingProvider(elastos-storage ipfs_streaming.rs) and unused publish profiles (publish.rs)Remove IPNS, discovery URI and HEAD_CID plumbing together (sources.rs, publish.rs, install.sh, release-signer.py, update-hop-compare.py, VERSIONING.md), and the→ moved to After 0.8.0 (PR Cleanup for 0.8.0: dead update code, unused providers, IPNS plumbing, one copy of install and isolation text (#89) #358)jetson-testchannel (9 places)Remove protected-content parts from the→ moved to After 0.8.0 (PR Cleanup for 0.8.0: dead update code, unused providers, IPNS plumbing, one copy of install and isolation text (#89) #358)homeinstall (elacity-player, media tools, protect/decrypt providers) while protected content is off; installed copies are left untouched by updates todayRun the model-management.js copy check in CI and the pre-push gate→ moved to After 0.8.0 (PR Cleanup for 0.8.0: dead update code, unused providers, IPNS plumbing, one copy of install and isolation text (#89) #358)One copy of the install text (docs/INSTALL.md; README and GETTING_STARTED link to it) and of the isolation block (7 copies today, State actual isolation in docs, manifests and release notes #170)→ moved to After 0.8.0 (PR Cleanup for 0.8.0: dead update code, unused providers, IPNS plumbing, one copy of install and isolation text (#89) #358)Replace the HTTPS Carrier-address lookup after install with Carrier-native discovery (Community works while any participant is online (open bootstrap and relay) #324)→ moved to After 0.8.0 (PR Cleanup for 0.8.0: dead update code, unused providers, IPNS plumbing, one copy of install and isolation text (#89) #358)
Activity
andersalm commentedon Sep 29, 2026
QA retest 2026-09-29 (published install vs release-head)
Verdict: STILL_REPRO — channel/version drift between published binary, update plan, and marketing.
Steps
/home/box/.local/bin/elastosfrom the public installer path.elastos --version,elastos update --check/upgrade --check.https://elastos.elacitylabs.com/release-head.jsonand 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
f6da8ce7db012fba4e8443fce372e0f8a8e6bdf4df1e84e50272396cfb87eba8update/upgrade --checkrelease-head.jsonpayload.versionEvidence
/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.
andersalm commentedon Sep 30, 2026
Paused on 30 Sep at 15:40 UTC (Codex weekly limit). State for the next thread:
47658723, with Irzhy's F3 fixed and the recovery proof recorded. Its CI run was cancelled at the pause, so rerun CI first.[-]0.7.1: Signed update[/-][+]0.8.0: Signed update[/+]andersalm commentedon Oct 1, 2026
QA Deployment 2026-10-01 (~08:49 America/Bogota) — WORSENED vs 2026-09-30
Published binary identity unchanged (
elastos 0.1.2, sha256f6da8ce7…eba8). New:update --check/upgrade --checkfail with Carrier connect timeout, andhttps://elastos.elacitylabs.com/release-head.json(plus/and/home/) return HTTP 502.Filed: #162. Local published Home smoke on
127.0.0.1:61201still HTTP 200.Evidence:
/workspace/elastos-qa-deploy-20261001-0848/.andersalm commentedon Oct 2, 2026
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_didspins the signer;publisher_node_id/connect_ticketselect 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.pyandscripts/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.
165 remaining items
andersalm commentedon Oct 16, 2026
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).
andersalm commentedon Oct 16, 2026
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 showprints "Head CID: unknown".andersalm commentedon Oct 16, 2026
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.
andersalm commentedon Oct 16, 2026
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).
andersalm commentedon Oct 16, 2026
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).
andersalm commentedon Oct 16, 2026
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.
andersalm commentedon Oct 16, 2026
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).
elastos update, alpha.21 → alpha.22): PASS, rc 0 in 51 s, Home 200 after 15 s;elastos home --browserbrings Community back.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).
andersalm commentedon Oct 16, 2026
Milestone sweep (16 Oct, alpha.22 = final candidate):
andersalm commentedon Oct 16, 2026
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.
andersalm commentedon Oct 21, 2026
OMP has prepared the unknown-component CLI and System test cases at
0a4cde4c2. The System test delta passed sys1 source review; kind2 delta review at992f71c67closes 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,4023ef12aandba224ca2b, 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 onba224ca2bfailed in 3m37s in the Home reload test. The configured Linux source gate at9382cd50epassed in 24m16s. New test-only commita6b52a808applies 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.andersalm commentedon Oct 22, 2026
The 22 October audit rechecked the Normal CLI rollback boundary on candidate
460b1888dand 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.andersalm commentedon Oct 29, 2026
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 (
5f65bee37and 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_seedinscripts/ci-installed-journeys.py, commit57627f88c): createElastOS/SystemServices/Publisher/artifactsin 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 in57627f88c..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/:cidread (Codex review ci1 on57627f88c).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.andersalm commentedon Oct 29, 2026
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 beendisabled_manuallysince 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.andersalm commentedon Oct 30, 2026
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.