Repository navigation
Fix release trust and prepare ShadowCode 2.3.3 - #15
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
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 2.3.2 tag could not be signed because the reviewed Linux trust policy allowed the production key only through 2.3.1. Prepare 2.3.3 and extend that existing key's interval through 2.3.3; preserve the unpublished 2.3.2 tag. Add a release configuration check that compares the candidate and independently reviewed policies and refuses a release outside the trusted key interval before either architecture build begins.
Validation: signing and publisher authentication tests pass locally (25 tests); UI typecheck passes. The full cross-platform CI and final release/package qualification are pending. A secret-free reproduction using the actual unsigned 2.3.2 handoff and a disposable matching key confirmed the prior interval rejected 2.3.2. The independent signing and verification implementations are unchanged.