fix(ci): set empty component to fix release-please auto-tagging#192
Merged
Conversation
…ging
release-please v4 derives an expected component ("gateway") from
`package-name: "@lobu/gateway"`. When the Merge plugin creates
a release PR, the title carries no component — so createReleases
sees `PR component: undefined != configured component: gateway`
and aborts without tagging. This has silently broken every release
since v3.3.0, requiring manual gh release create + label swap +
workflow_dispatch each time.
Removing `package-name` eliminates the expected component entirely.
The field was only cosmetic here (npm publish uses each package's
own package.json name, not this config key).
release-please v4 auto-derives the component from the root
package.json name ("lobu-monorepo") when no explicit component or
package-name is set. This still causes the "PR component: undefined
does not match configured component: lobu-monorepo" check in
createReleases. Set `component: ""` explicitly so release-please
expects no component and the merged PR title can match.
|
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
Merged
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.
Follow-up to #190. Removing
package-namemade release-please fall back to the rootpackage.jsonname (lobu-monorepo) as the expected component — same mismatch, different name.Setting
"component": ""explicitly tells release-please there is no expected component, so the merged PR title doesn't need to carry one.Test plan