chore: open the release PR as a draft#12
Merged
Merged
Conversation
jlav
approved these changes
Jun 25, 2026
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.
What
Add
"draft-pull-request": truetorelease-please-config.jsonso this repo's ownchore(main): release X.Y.ZPR opens as a draft.Why
This adds a deliberate "ready to ship" gate: a draft PR can't be merged, and merging the release PR is what publishes the release. So someone has to explicitly mark it Ready for review before it can be merged — a useful checkpoint before cutting a release.
Notes
draft-pull-requestis a release-please config-file option (not an action input). The action runs in manifest mode and reads it fromrelease-please-config.json, so this one line is all that's needed.