Authorize retained 1.7.9 release repair with public qualification waiver - #247
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
1 participant
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 retained v1.7.9 build passed its automated release validations, but publication stopped because the signed full-product qualification receipt was absent. Following the owner's October 1 approval, this change adds an explicit, default-false repair exception bound only to
v1.7.9atc6871b9bf506eec6cebe96beee1ac252429a7b99.The exception reuses the retained wheel, source archive and public evidence. It requires protected environment review, exact artifact checks, public waiver disclosure before PyPI publication, and complete PyPI file identity verification. Combined flags, other versions and changed tag commits are rejected. Ordinary publication still requires signed qualification; mandatory full-product acceptance gates remain unverified.
Validation: 65 focused release tests passed (62 Linux Bash cases skipped on Windows); 112 guard cases passed separately with real Git Bash and a credential-free GitHub stub; repository Ruff and diff checks passed. Independent integration review found no defects. Fresh PR CI is required before merge.