fix(ci): let release-please parse back its own release pull request - #18
Merged
Conversation
`pnpm release:tag` tagged nothing and returned `[]`. The reason was in the
warnings it printed:
PR component: undefined does not match configured component: renderizr
`github-release` finds the merged release pull request and parses its title to
recover the version and component. The configured pattern was
`chore(release): ${version}`, which contains neither `${scope}` nor
`${component}`, so parsing yielded an undefined component while the package
name `@formula-monks/renderizr` implies `renderizr`. They never matched, so no
release was ever built — silently, with an empty array rather than an error.
Restores release-please's own default pattern, which round-trips. The tag stays
`vX.Y.Z` because `include-component-in-tag` is false.
v1.1.0 was tagged and released by hand in the meantime, so this is about the
next release working through the tool rather than around it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
| Commit | Scanned at | New | Resolved | Net |
|---|---|---|---|---|
6fb83d9 < |
2026-08-17 02:07 UTC | 0 | 0 | 0 |
Last scanned: 6fb83d9 · 2026-08-17 02:07 UTC
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.
pnpm release:tagtagged nothing and exited successfully with[]. The reason was buried in its warnings:Cause
github-releasefinds the merged release pull request and parses its title to recover the version and component. The configured pattern was:No
${scope}, no${component}. So parsing yielded an undefined component, while the package name@formula-monks/renderizrimplies a component ofrenderizr. They never matched, so no release was ever built — silently, with an empty array rather than an error, which is why it looked like it had worked.Fix
Restores release-please's own default pattern, which round-trips:
The tag stays
vX.Y.Z—include-component-in-tagisfalse.Context
v1.1.0 has been tagged and released by hand: https://github.com/FormulaMonks/renderizr/releases/tag/v1.1.0
This is about the next release going through the tool rather than around it. Worth noting the failure mode for whoever hits it next:
release:tagreporting[]is not "nothing to release", it is "I could not match the release pull request".🤖 Generated with Claude Code