Repository navigation
chore(release): release-prepare counts the pull requests merged into a milestone branch - #198
Merged
Merged
Conversation
…a milestone branch Change pull requests target a milestone branch (release/next) instead of main; its one pull request into main is the release, so one approval covers the milestone. On that branch, release-prepare now takes the version and the notes from the pull requests merged into it (plus main since the last tag); the branch's own pull request title counts only on a feature branch with none. README describes the flow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Change pull requests now target the milestone branch
milestone/next(milestone "Next release") instead ofmain. The developer merges into it only what is meant to ship, and its single pull request intomainis the release, so one approval covers the whole milestone.What changes in
bin/release-prepare. Run on a milestone branch, it now takes the version and the notes from the pull requests merged into that branch (its first-parent history abovemain), together with whatmainholds since the last tag.maininto the branch and the release bump commit are left out.The README "Releasing" section describes the flow.
Tests.
bin/release-prepare-testgains 7 milestone checks:feat;The whole harness passes.
Not a release.
🤖 Generated with Claude Code