Repository navigation
chore(security): regenerate the approved publish-workflow revisions - #5160
Conversation
@codex review |
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. |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
Exact-head evaluation: The native regeneration run 39523414940 succeeded on the merged implementation. This PR changes only the observed Native PR CI 39523516815 completed successfully at this exact head. Codex completed its exact-head review with no findings; all review and comment surfaces were read with complete pagination and no unresolved threads. The programmed-updater exemption does not apply, so this is ordinary protected review, not an exemption. No code from this bot-authored branch was executed locally. Correctness, simplification and security review found no additional changes needed: this is an observation update, not a publisher-approval change. The independent code-quality ruleset is not readable through the API; it remains enforced by GitHub's protected merge decision. |
Merged through the normal protected queue as Independent live readback confirms the maintained catalogue artifact at 7.23.0 with the expected immutable digest, current observed generation, Ready and SourceVerified true. This closes the generated observation update; it does not assert that every remaining legacy consumer has been migrated or that retirement is already cleared. |
Why
The cluster only trusts releases signed by publishing-workflow revisions it
has approved. A consumer's deployed release or workflow pin has moved,
so the approved list is out of date.
What
Refresh the approved list and each consumer's matcher from what is deployed
and what each consumer currently pins. Every consumer resolved on both halves,
and each matcher accepts exactly its approved revisions.
No issue: trivial fix.