Repository navigation
chore(release): bind the v1.3.1 verification block to the readiness run of 39aaa4e - #398
Merged
Merged
Conversation
There was a problem hiding this comment.
An organization admin can review the limit in your organization's usage and billing settings.
Once the limit resets or is raised, reopen this pull request to trigger a 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. |
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 first v1.3.1 tag failed release.yml's verify-ci gate: the verification block cited readiness run 36307403853 (evaluated at a6fc9d9), but the tagged commit also carried the #385 same-key forms fix (3612f0d), and only Cargo.toml/Cargo.lock/CHANGELOG.md may change after the readiness run.
Release-readiness was re-run against 39aaa4e (run 36309366056, pass). This PR rebinds the block to that run; CHANGELOG.md is the only change. After merge and green exact-main CI, v1.3.1 is retagged on the new main commit (nothing was published from the failed run, so moving the tag is safe).