chore: back-merge main into next after 0.8.13 - #591
Open
sotashimozono wants to merge 1 commit into
Open
Conversation
Promotion: next → main (0.8.13-beta.17, no cut yet)
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
ADR-0025 §D6 rule 4: anything landing on
mainis back-merged so the beta lane never regresses.Opened by hand because
backmerge.ymlcould not:That is #426, and this is the fourth consecutive failure (2026-08-27, 08-29, and twice today around the 0.8.13 promotion). The workflow prints the fix itself: re-mint the fine-grained PAT with a lifetime <= 366 days (contents + pull-requests: write) and update
RELEASE_PLZ_TOKEN, or move to a GitHub App installation token to stop it recurring on every expiry.Content
No file differences.
mainis exactly one commit ahead ofnext— theMerge pull request #580commit itself, which carriednext's own tree ontomain. This aligns the graph so the next comparison is clean; it changes no file.Because there is no diff, the usual
Cargo.toml/Cargo.lockversion conflict that back-merges hit (next carrying-beta.Nagainst main's clean stable) does not arise here:nextis also at0.8.13, since the cut landed there first this cycle.