Stop silently dropping eligible PRs from patch release preparation#9640
Merged
Conversation
The patch-release PR scan only looked at master, so a fix merged straight onto the stable branch through a dedicated backport PR was never discovered and its changelog entry was dropped. Also scan the stable branch since the last release, and skip cherry-picking those PRs since they are already on the release branch. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
prepare! discovered PRs and branched off the local master and stable refs, so a clone that had not pulled the latest master silently left freshly merged PRs out of the release. Fetch origin up front and work from the remote-tracking refs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
hsbt
added a commit
that referenced
this pull request
Jun 23, 2026
Stop silently dropping eligible PRs from patch release preparation
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.
The patch release scan only looked at master, so a fix merged straight onto the stable branch through a dedicated backport PR was never discovered and its changelog entry was lost. It now also scans the stable branch since the last release and skips cherry-picking those PRs because they are already on the release branch.
prepare! also branched off the local master and stable refs, so a clone that had not pulled the latest master left freshly merged PRs out of the release. It now fetches origin up front and works from the remote-tracking refs.