Repository navigation
ci: prepare isolation and verify exact released versions - #829
Merged
Merged
Conversation
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
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.
Homebrew installation CI could accept the previous release when its matching formula and binary were installed before the asynchronous tap update. Native ARM64 release validation also assumed writable controller paths, a specific progress banner and GNU checksum tools on macOS.
Resolve one published version for all installation jobs, wait for that exact tap version without pre-tapping, and reject stale or mismatched installed versions. Preserve Homebrew upgrade errors. Prepare native bwrap with the published xlings isolation doctor and place cold consumer state within the selected SubOS instance's writable subtree. Assert the default ARM64 toolchain through the public build-database output and use each target platform's native checksum command.
The verification consumes the sealed public release, retains controller read-only isolation and the hidden host checkout, and requires actual native builds, deployment, ecosystem consumers and execution of all three cross-target artifacts. It adds no product compatibility behavior or new manifest fields.
Closes #828
Validation:
The product changes, specifications, documentation and release version were delivered together in #827. This follow-up maintains release verification; tag v2026.10.21.1 and its published assets remain unchanged.