fix(ci): put version in release-please PR title#176
Merged
Conversation
Without a \`pull-request-title-pattern\`, release-please v4 generated
release PR titles of the form \`chore: release main\` — no version
in the title. After merging, release-please couldn't parse its own
merged PR to determine what version to tag, aborting with
"untagged, merged release PRs outstanding". That's what blocked
both 3.1.0 and 3.1.1 from flowing through the release-please
publish job end-to-end (had to manually publish each via
\`gh workflow run publish-packages.yml\`).
Set \`pull-request-title-pattern\` to \`chore(main): release \${version}\`
so the PR title matches the old working format and release-please
can extract the version post-merge. Also add \`workflow_dispatch\`
to \`release-please.yml\` so the workflow can be re-triggered
manually without pushing a dummy commit when the state needs a
kick.
This was referenced Apr 11, 2026
Closed
Closed
Closed
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.
Summary
release-please v4 without a custom `pull-request-title-pattern` generates release PRs titled `chore: release main` — the version is NOT in the title. On merge, release-please can't extract the version from its own PR and aborts with "untagged, merged release PRs outstanding", preventing the publish job from firing automatically.
Set `pull-request-title-pattern` to `chore(main): release ${version}` to match the old working format. Add `workflow_dispatch` so the workflow can be re-triggered without a dummy commit.
After this lands, the next `feat:` / `fix:` will produce a release PR titled `chore(main): release X.Y.Z`, and merging it will tag + trigger `publish-packages.yml` automatically.
Test plan