chore: drop component prefix from release-please tag pattern#16
Merged
Conversation
release-please was tagging llm-tracker-v0.2.0 (single-package default), but publish.yml listens for v*.*.*. The mismatch meant the 0.2.0 release tag didn't trigger npm publish. Fixed for future releases by setting include-component-in-tag=false so tags are plain v*.*.*. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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` with a single-package `{"."}` config defaults to tagging as `-v*..` — in our case `llm-tracker-v0.2.0`. But `publish.yml` listens for `v*..` only, so the 0.2.0 release tag did not trigger npm publish.
Workaround for 0.2.0: I manually created a `v0.2.0` tag on the same commit and pushed it, which fired the publish workflow.
This PR is the permanent fix — adds `"include-component-in-tag": false` so future release-please runs emit plain `v*..` tags that match the publish trigger out of the box.
Test plan