Repository navigation
Require compiler acceptance before releasing 0.4.3 - #11
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 guarded release workflow could prepare or verify a draft without requiring the compiler workflow that proves the C# coverage correction. Add compiler-execution.yml to the exact-main prerequisites; missing, failed, active, differently sourced or PR-only compiler evidence must block release preparation and final verification.
Independent response-mutation tests cover those failures and ensure no draft is created when compiler acceptance fails. Release notes now explain data preservation, checksums, unsigned packages and the separate Docker prerequisite. No product runtime or account format changes.
Validation: 112 focused release/draft tests and 28 subtests passed. Ruff and 97 source-map checks passed. Final main compiler, validation, security and native-package workflows must pass before release dispatch. The owner's Docker setup and account data are unchanged; a fresh private backup has been verified for the subsequent installation.