Repository navigation
ci: complete 0.0.10 release gates and verify production image boot - #38
Open
ultronstudio wants to merge 2 commits into
Open
ultronstudio wants to merge 2 commits into
ultronstudio wants to merge 2 commits into
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
This branch has not been 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
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.
RC2's release gate ran 22 QEMU scenarios even though the source audit recorded 34 local passes. This restores the 12 omitted process, ELF, user-copy and isolation scenarios to both build and runtime matrices, adds the 15 host filesystem tests and Python tooling tests, and fails CI when a standalone Cargo scenario lacks runtime coverage.
CI now also builds a production release image without test features and boots it directly. Both RC and stable packaging repeat the smoke check on the exact image being published before checksums and attestation. Success requires ordered Boot:/PID 1/CPL3 serial evidence and an observation window; timeout, early exit, fatal diagnostics and the test-only initrd marker fail. Snapshot writes and a SHA-256 check protect the input image.
Stable publishing now rejects an Unreleased changelog entry. Release policy, testing documentation, roadmap and changelog describe the corrected gates and RC3 preparation. Version stays 0.0.10 and remains Unreleased pending final release preparation. The historical source audit is unchanged.
Validation completed locally:
The full local QEMU matrix passed 34/34 scenarios, using each feature selection from the updated workflow and requiring exact isa-debug-exit status 33. GitHub checks independently run the updated gates. No RC or stable release is published by this PR. The required-reviewer configuration of the GitHub release environment remains a separate, unverified repository setting.