fix: use per-package tags in release-plz #107
Merged
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
Using a shared tag
v{{ version }}caused release-plz to skip publishing packages because it assumed all packages were already released when the tag existed.Switch to per-package tags
{{ package }}-v{{ version }}so each package has its own release tag (e.g.,s2-cli-v0.26.0,s2-api-v0.26.0).Test plan
🤖 Generated with Claude Code