chore(release): allow release-please to be triggered manually - #9
Merged
Conversation
release-please only reconciles its release branch on a push to main. When an unrelated commit lands after the release PR is opened, that PR can end up conflicting with main and there is no way to ask release-please to redo it — v0.14.1's release PR hit exactly that after a docs change touched package.json's description alongside the version bump. workflow_dispatch gives a way to regenerate it without pushing a filler commit.
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.
release-please only reconciles its release branch on a push to
main. PR #8 landed after release PR #7 was opened and touchedpackage.json's description, which collides with the version bump on the release branch — leaving #7mergeable=falsewith no way to ask release-please to redo it short of pushing a filler commit.workflow_dispatchgives that a proper trigger.Merging this also pushes to
main, which regenerates #7 on top of current main as a side effect — so it fixes the immediate conflict and prevents the next one.