2.2 KiB
2.1.2-beta application OTA acceptance
Frozen source: 92b1f54a153d3899e56462789ca945ac066f7569.
Signed manifest SHA256: 9b70a0ad07708f19a6eba131bbaccbefafa8b2890cc2d8a5a0c04e65e991ba3e.
The production backend and dashboard were built from the clean annotated release tag. The independently appointed verifier authenticated the signed manifest against the pinned release root. Canonical and Gitea source/tag parity passed.
An installed 2.1.0-beta.2 node authenticated and applied this exact signed application-runtime update. Supported recovery restored the prior version, and a repeat signed update committed successfully. Independent checks matched the running backend, served dashboard/provider, transaction-owned frontend tree and runtime record. Wallet, identity and payment state, app installation decisions, container identities and peer trust/removal records were preserved. Peer sync timestamps and remote status are compared separately from authoritative connection policy. The first overly coarse peer-state hash failure remains in the private evidence; it is not represented as a preservation pass.
The dashboard payload matches the previously maintainer-approved mobile and desktop build. Existing app/payment and Bump28 phone acceptance remain pinned to their recorded artifacts; this does not claim new payment, physical-device, fleet-wide or ISO testing.
The feed is promoted only after full public downloads match every signed component hash and size and Companion Bump28 is publicly downloadable. OTA artifacts are uploaded first, followed by the APK, then update availability is enabled for nodes. ISO qualification remains separate; new first-install account/Wi-Fi setup and optional runtime hardening are deferred.
Rollout hold
Update advertising is reverted to the previous signed feed while first-generation upgrades from 1.9.1-alpha and earlier supported releases are qualified. An actual 1.9.1-alpha upgrade exposed a missing signed historical-manifest asset; repeated pre-admission retries consumed system-partition space. The successful installed tests above covered the newer public owner and did not qualify this older path. APK availability is independent of this OTA hold.