Enable verified automatic updates for the native CLI - #220
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ALGAL’s supported native installs gain automatic updates, enabled by default, and
algal updatecommands to check, install, inspect, enable, or disable them. Updates verify the immutable release, platform assets, full compiled tag and source commit, archive contents, release metadata, and Mac signature before an atomic replacement. Pins, saved preferences, running commands, SDK executable hashes, and rollback are preserved.The native installer delegates verified installation to the new executable. Source/Bun installs keep their existing workflow. Help, offline commands, CI, and explicit opt-outs skip automatic checks. Release publication now fills a verified draft by asset ID and safely verifies retries after uncertain publication without replacing existing assets. The website’s published-release record stays on the currently available release until vm.13 is published.
Validation: independent source review,
bun run check(1,901 tests, TypeScript, lint, docs, and 74-page site build), workspace formatting, strict Clippy, Rust tests/build, all six native parity suites, and native packaging/install fixtures passed for the implementation at05b7f012. All 45 release-notes, publisher, and workflow tests passed. CI at final head11fed51dpassed all 19 jobs, including native demos, parity, browser contracts, and the three release platforms.CI's demos now reuse the existing optimized parity artifact, which retains debug assertions and overflow checks. SDK children still verify their executable hash and all deadlines remain unchanged. The previous unoptimized inventory run hit its 30-second deadline; the corrected run took 5 seconds. Native-demo job wall time changed from 82 seconds (failed) to 49 seconds (passed), with one observed run per variant; this is not a repeated benchmark.