fix(ci): restore release-please pull-request-title-pattern#186
Merged
Conversation
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.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This was referenced Apr 16, 2026
Closed
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
pull-request-title-patternthat was dropped in feat: refresh cli docs and restore release publish chain #179, so release-please can parse its own merged PR's component and cut the tag + GitHub release.Root cause
Log from release-please after merging v3.4.0's release PR:
createReleases bails, then the next run sees the merged PR still carrying
autorelease: pendingand aborts with "untagged, merged release PRs outstanding".Restoring the pattern makes release-please title PRs
chore(main): release 3.4.1— matches${scope}/${component}/${version}— and round-trips cleanly.Test plan
chore(main): release X.Y.Zv*tag + GitHub release created automaticallypublish-packages.yml+ Docker dispatched without manual intervention