Repository navigation
Prepare RC qualification and close release-gate coverage gaps - #20
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.
The release qualification command scanned only the runtime/development locks and silently defaulted to an old alpha upgrade baseline. It now checks all four installed environments, verifies embedded verifier pins, and requires an explicit, different previous release for full qualification.
Adds nine tooling regressions on both hosted platforms and a separate beta-to-RC/stable qualification plan. Historical alpha release candidates are explicitly separated from the proposed 0.20.0-rc.1. Documents artifact/upgrade/observation gates and the website-before-Pinokio publication dependency.
Validation: tooling tests passed twice; core suite 3453 passed / 3 platform skips; desktop 101 passed; 277 adversarial and 44 real-model E2E cases passed; all four lockfiles OSV clean; public hygiene clean. Full published Beta.9 clean installation and Beta.8→Beta.9 signed upgrade/migration/rollback passed with operator-state and schedule read-back. Both native PR-CI jobs passed.
No runtime, permission, dependency, version or operator-state change. This prepares qualification; it does not publish or claim a qualified RC/stable artifact.