Repository navigation
Requalify the exact Compose payload for the existing OpenPGP decision - #412
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 publisher correctly rejected the new Compose executable because the existing OpenPGP exclusion was still bound to the 0.14.40 binary. Requalify the original 0.14.41 release bytes and update only that exact hash and its impact statement; executable paths, module versions, consumers and policy thresholds remain unchanged.
The versioned evidence binds the official CI/release bytes, source and vendor graph, with zero OpenPGP entries among 390 source packages, 21,993 emitted functions and 26,700 function/inline-name entries. bcrypt/scrypt positive controls are present. This is code absence, not a claim that the crypto module was fixed. The previously failed producer-pin check and one new cross-file qualification contract passed; unaffected functional tests were retained. Server565 remains unpublished until the required checks and publisher succeed; QA8080 and production are untouched by this correction.