Repository navigation
Release 2.0.1 #535
Description
2.0.1
Target: 2.0.1-rc.1 on test versions on Fri 6 Nov, then 2.0.1 stable from the same build at the weekend (Anders, 5 Nov). A failed check moves the date.
Scope
- On develop: Chat and open apps stay connected and reconnect by themselves (Open apps, including Chat, stay connected while Home runs and reconnect by themselves #532); Browser Close no longer fails on a busy port (Browser Close no longer fails when another program uses a port in the media relay range #526); Assistant keeps a finished reply in view (CI reliability: the census names the child that left its unit (#433); Assistant keeps the finished reply in view #533); release scripts keep the GitHub token off the command line (Release scripts keep the GitHub token off the command line #529); CI reliability (CI: three flaky checks wait, time out clearly, or free disk first #530, CI reliability: the census names the child that left its unit (#433); Assistant keeps the finished reply in view #533).
- Browser on the Jetson and other Linux ARM64 hosts with KVM (G5 Private Browser: Jetson support #90, Browser on the Jetson: per-launch overlay instead of a disk copy (#90) #531). Anders's decision, 5 Nov: in 2.0.1, although docs/VERSIONING.md counts a new platform artifact as a minor change.
- Browser on Linux is opt-in for 2.0.1: install.sh no longer runs the Browser administrator setup or the 900 MB download; one command turns it on, and opening Browser shows that command (Anders, 5 Nov: Browser from Marketplace, not install.sh; the Marketplace Get is Marketplace: Get for apps, not only models #333 in 2.1.0).
- In progress: Community room sessions end with the person's session (PR from fix/room-session-bound); installer fixes Installer refuses an older Linux Home whose files are group-writable or owned by root #516 and Install command refuses a running Home when the time locale is not English (strptime on ps lstart) #517; update retries only an unreachable source (fix/2.0.1-update-status); System, About lets the owner choose Stable or Test versions for updates, approved in Inbox.
Not in 2.0.1
- Update fails on Homes with the local AI engine: sealed llama.cpp tree cannot be replaced (2.0.1) #515 (Mac local AI update with a changed engine archive). Guard: 2.0.1 ships the same local AI engine archives as 2.0.0, checked before signing.
- Browser image admission trusts digests in the installed image directory #534 (Browser image digests read from the image directory; pre-existing since 2.0.0 on Mac): needs a reasoned release hold or no-hold decision now that Linux ARM64 ships the same admission.
Done means
- All scope PRs merged to develop with CI green and their reviews recorded.
- Release prechecks cover the linux-arm64 Browser image (ops: alpha-lib.sh musl_check, musl-precheck.sh); local AI engine archives equal 2.0.0's.
- 2.0.1-rc.1 named, package run and qualification pass, Anders signs, published on test versions.
- Installed checks on rc.1: fresh install and update from 2.0.0 on Mac and Linux x86/ARM; Mac with local AI updates; Jetson: one-time Browser setup, update from 2.0.0, Browser opens, profile kept through the update, Undo.
- 2.0.1 stable from the same build, signed, published; GitHub release page.
Activity
andersalm commentedon Nov 5, 2026
#534 has a scoped no-hold disposition for 2.0.1: the reported attack requires prior host-account write access. Its signed-digest repair stays open, and the decision changes if the path crosses confinement, account or privilege boundaries.
Keep #406’s signed helper-byte gate and the existing #90 installed/media/manual/human acceptance. Anders’s Jetson/channel steering changes the release scope; it grants the existing owners their work and preserves the signing/publication approvals.
Main owns the exact candidate, current reviews/checks, unchanged 2.0.0 engine-archive check and installed qualification before release. Earlier #515 work remains open under the new release order.
andersalm commentedon Nov 5, 2026
Room-session PR #536 has bounded independent source PASS, with grant-bound expiry and legacy-record refusal traced through its use paths. The exact completed full Linux receipt was read; execution remains owner evidence.
Main owns current checks/reviews and integration, followed by the installed sign-out/reconnect and release qualification in #86 and this issue. Private advisory contents remain private.
andersalm commentedon Nov 5, 2026
For the Linux opt-in scope, verify the complete fresh-install path: install.sh and opening an unprepared Browser show the explicit setup command while leaving acquisition and administrator setup to that command. Runtime’s current local-engine preparation happens before the readiness probe, so changing install.sh alone does not establish this behavior.
The explicit command still needs #406’s signed-byte binding for the privileged helper. Preserve existing prepared installations and Browser profiles, then qualify first setup, Open, Close/reopen, update and Undo on the release candidate under #90.
Anders’s Marketplace request is confirmed at origin; the terminal command for 2.0.1 and #333 Marketplace work are Main’s recorded implementation stages. Source review waits for their frozen candidate and completed checks.
andersalm commentedon Nov 5, 2026
The push queue reports that the Linux Browser opt-in candidate
ac38aa17eis waiting for its required full Linux check. This is a missing completed receipt, rather than a reported test failure.Main owns the next action: use the existing remote-check queue and an available owned slot, preserve any failed attempt, then supply the completed full-check receipt with the full commit, tree and base. Main continues the normal review and integration gates; Root reviews the frozen source and completed evidence when supplied. The fresh-install refusal, explicit setup/Open/Close, profile and update/Undo acceptance checks remain in scope.
andersalm commentedon Nov 6, 2026
Main reports that the old 2.0.0 Cargo build cache was removed after its final process/open-file check, and both lifecycle inventory rows were marked removed. Reported free space is 63,920,976 KiB, above the reported 52,468,949 KiB stop line. The channel chooser’s previously refused Clippy and all-target checks are resuming. This is completed owner evidence; Root’s earlier independent check established zero tracked paths and zero open files before releasing cache protection.
The queue now reports one untriaged late failure and Browser opt-in candidate
10dec7c60waiting for its required full Linux receipt. Main owns failure triage from the actual error, any repair and check scheduling in the existing lane. The changed candidate needs its own completed receipt and frozen review. These source/check steps remain separate from installed release acceptance.andersalm commentedon Nov 6, 2026
Root SOURCE REVIEW: CHANGES REQUIRED on
f1232e148f2b1d0ab8ab9ee03d63e9c3e366aab2/ tree3de15aca32bce6ea2c4f63ea0809a521f2539270, base527a193cca91dcf8cce37e0d721f436071f580c7(17 changed files). Independent Browser status 17/17 and four focused installer cases pass, zero skipped; candidate-attribute diff check passes. The first narrow installer invocation used unsupported test arguments and ran zero tests; the corrected module invocation passed. The completed full Linux receipt matches this head/tree/base and reports PASS; execution remains owner evidence. Root ran zero Rust builds/tests or target operations.P1, #406:
setup/browser_linux.rs:37–53,158–185still leaves the privileged helper handoff without an exact binding to the admitted bytes. Main must complete #406’s replacement regression and repair that handoff before claiming this manual setup meets the existing release gate. Details stay with Main’s private review delivery.P2,
api/gateway_browser.rs:618–623/setup/browser_config.rs:191–224: an already open Browser viewer whose native supervisor is missing or stale receives setup guidance before it reaches the helper repair path. The new helper-refresh tests call the producer directly and miss this consumer ordering. Main should keep the early fresh-Home refusal, allow admitted helper repair for an already configured Home before the host probe, and test actual Browser Open with missing/stale helpers after the viewer is loaded. Installed setup/Open/Close/profile/update/Undo acceptance remains open.