Repository navigation
Open
Labels
P2Follow-up: acceptance, robustness and integrationsFollow-up: acceptance, robustness and integrationsenhancementNew feature or requestNew feature or request
Description
Priority: P2 · Updated 2026-10-26. Published-beta acceptance and hardening umbrella.
Verified delivery
- Public v0.1.0-beta.1 and v0.1.0-beta.2, published by the maintainer on 2026-10-26.
- Six Windows/Linux/macOS x64/ARM64 archives, manifest/hash/checksum verification and embedded documentation/licenses.
- Beta.2 single-file format-2 packages, per-user install/PATH and owned uninstall (Add single-file bundles and per-user installation with optional PATH #22).
- Native Windows x64/Linux x64/macOS ARM64 CLI/install/helper/startup-probe/rollback smoke; other architectures are cross-built, not physically certified.
- Maintainer reports beta.2 local retest looks good. Record further acceptance specifically rather than inferring every scenario.
- Draft-only automation preserves manual publication. Persistent preferences/Home changes (Persist defaults and improve Home and form recovery #24) are newer than published beta.2.
Remaining work
- Measure and reduce CLI startup latency and distribution size #25 (P1): measure/reduce startup latency and executable/archive/cache size; separate cold extraction, warm startup and app initialization.
- Evaluate Native AOT and trimming for smaller, faster standalone releases #26 (P2): measured Native AOT/trimming feasibility and deployment decision.
- Validate the complete updater against published beta assets #53 (P2): complete public updater lookup/download/prepare/helper/caller-exit/replacement/status acceptance in isolated installations.
- Preserve user files changed between update Prepare and Apply #54 (P2): preserve/refuse user-file mutations between Prepare and Apply before strengthening preservation claims.
- Evaluate Windows signing and macOS signing/notarization #51 (P2): Windows/macOS signing/notarization and publisher-trust decision.
- Prevent duplicate release drafts for an already published version #57 (P2): investigate the extra beta.2 draft and prevent duplicate drafts for published versions.
- Execute remaining architecture packages on native hardware and record actual OS/architecture results; retain fresh-system install/remove acceptance in Installation and hook migration: finish first-run and repair #18/Guide first-run installation, output setup and first state delivery #31.
- Evaluate package-manager distribution and package identities #52 (P3): package-manager channels, names and update ownership.
Release constraints
Beta.1 uses format-1 directory packages and cannot update itself to format 2; use the documented manual transition via beta.2's new installer. Stop a running host before binary replacement. Scheduling a helper is not successful completion; confirm receipts/startup and keep recoverable backups.
Checksums detect corruption, not compromise of the publisher. Builds are unsigned until #51 is implemented. Release preparation must preserve manual publication and never replace an already-published version's assets. No further release is published by this issue triage.
Metadata
Metadata
Assignees
Labels
P2Follow-up: acceptance, robustness and integrationsFollow-up: acceptance, robustness and integrationsenhancementNew feature or requestNew feature or request
Activity
[-]M3: Build verified self-contained Windows releases[/-][+]M3: Validate cross-platform releases and verified self-update[/+][-]M3: Validate cross-platform releases and verified self-update[/-][+]Release acceptance and updater hardening[/+]