chore(release): add scoped v1.7.6 waiver path - #236
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9684e74bc0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: db51274a8e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3142d7bbae
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
The manual release repair path supports the owner-requested qualification exception for existing
v1.7.6at commit6a441a75c8dd159607fa3933da83f600864b9146. The option defaults to false, retains the protected environment, and cannot exempt a different version or reused tag commit. Normal publication and other repairs still require signed qualification.The waiver is publicly disclosed in GitHub Release notes before the first PyPI write. A failed notice write stops publication, and a later repair failure leaves the disclosure visible. GitHub assets are exposed only after the notice, with latest-release promotion following successful publication. No unverified qualification gate is represented as passed.
The benchmark prerequisite fix now retries only a verified legacy PID inode removed after opening. Pre-open disappearance, inode replacement, inaccessible files, and removed persistent markers remain unsafe. Deterministic between-probe synchronization removes the flaky test race. Fresh immutable v76 evidence binds the changed source without rewriting historical reports.
Validation:
The owner instruction recorded when this PR was opened concerned only the v1.7.6 repair; retained build artifacts came from run #35837561367. These code changes do not themselves dispatch, approve, or publish a release.