Repository navigation
fix(publish): approve the v21.0.1 publisher for organization settings - #6064
Merged
Merged
Conversation
Rotate the github-config cosign matcher to the pair {applied 1a0eb6f (v20.1.17),
next 933b536 (v21.0.1)}, so devantler-tech/.github#902 can update its signed
caller without breaking verification of the deployed artifact.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
@coderabbitai review |
Contributor
Action not completed
|
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 52 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
Contributor
Author
@codex review |
Codex Review Summary: ✅ CompletedThis 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. Swish! 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". |
Contributor
✅
|
Contributor
✅
|
Contributor
Author
Readiness at
After merge: confirm Flux re-verifies the deployed artifact under the new matcher, then update the caller pin on devantler-tech/.github#902. |
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.
Why
The organization-settings repository wants to move to the newest release of the shared publishing workflow, but its own safety check refuses that move until the platform already trusts the new release as a signer. Without this, its pending update (the organization-settings update PR) stays red and organization settings cannot be republished.
What
The platform now trusts exactly two publisher releases for organization settings: the one that signed what is running today, and the new release the pending update moves to. The oldest previously trusted release is dropped, so the trusted set stays at two.
Fixes #6063