fix(ci): use default release-please title pattern variables#178
Merged
Conversation
release-please v4 warns and falls back to the default title when
the custom pull-request-title-pattern is missing ${scope} and
${component} placeholders. Use the canonical pattern
`chore${scope}: release${component} ${version}` which evaluates
to `chore(main): release 3.1.2` for the single-component root
package and matches the format of the old tagged release PRs in
history.
buremba
added a commit
that referenced
this pull request
Apr 16, 2026
Without an explicit title pattern, release-please v4 generates
"chore: release main" and the PR title carries no ${component}.
When the PR is merged, createReleases then fails its post-merge
match check:
⚠ PR component: undefined does not match configured component: gateway
so the tag + GitHub release are never cut. The candidate-PR phase
then aborts with "There are untagged, merged release PRs outstanding",
blocking every subsequent release until the label is manually fixed.
That regression was introduced in #179 (dropped the pattern added in
#178). v3.3.0 and v3.4.0 both required a manual recovery (tag + release
+ relabel + workflow_dispatch publish). Restore the canonical pattern
so release-please produces titles like "chore(main): release 3.4.1"
which it can parse back after merge.
buremba
added a commit
that referenced
this pull request
Apr 16, 2026
Without an explicit title pattern, release-please v4 generates
"chore: release main" and the PR title carries no ${component}.
When the PR is merged, createReleases then fails its post-merge
match check:
⚠ PR component: undefined does not match configured component: gateway
so the tag + GitHub release are never cut. The candidate-PR phase
then aborts with "There are untagged, merged release PRs outstanding",
blocking every subsequent release until the label is manually fixed.
That regression was introduced in #179 (dropped the pattern added in
#178). v3.3.0 and v3.4.0 both required a manual recovery (tag + release
+ relabel + workflow_dispatch publish). Restore the canonical pattern
so release-please produces titles like "chore(main): release 3.4.1"
which it can parse back after merge.
buremba
added a commit
that referenced
this pull request
Apr 16, 2026
…#188) * fix(ci): restore release-please pull-request-title-pattern Without an explicit title pattern, release-please v4 generates "chore: release main" and the PR title carries no ${component}. When the PR is merged, createReleases then fails its post-merge match check: ⚠ PR component: undefined does not match configured component: gateway so the tag + GitHub release are never cut. The candidate-PR phase then aborts with "There are untagged, merged release PRs outstanding", blocking every subsequent release until the label is manually fixed. That regression was introduced in #179 (dropped the pattern added in #178). v3.3.0 and v3.4.0 both required a manual recovery (tag + release + relabel + workflow_dispatch publish). Restore the canonical pattern so release-please produces titles like "chore(main): release 3.4.1" which it can parse back after merge. * fix(ci): use simpler release-please title pattern that actually works The canonical `chore${scope}: release${component} ${version}` pattern trips release-please v4's own "miss the part of '${scope}'" warnings and falls back to `chore: release ${branch}` — which leaves the merged PR title with no version, breaking the post-merge component match and blocking tag creation. Use the simpler `chore(main): release ${version}` pattern that actually produced working titles in #175 / #177 (e.g. `chore(main): release 3.1.1`).
This was referenced Apr 16, 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.
Fix the title pattern so release-please actually applies it. Evaluates to
chore(main): release X.Y.Zfor single-component root packages.