fix: derive npm publish version from release tag - #13
Merged
Conversation
The release workflow published the literal package.json version instead of the tag, so the two drifted (v0.4.0-rc.1 shipped to npm as 1.0.0). Now derive the version from the git tag and keep package.json at a 0.0.0 placeholder, matching qstash-cli.
CahidArda
approved these changes
Jun 25, 2026
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
2 participants
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.
Release workflow published the literal
package.jsonversion, not the tag — so they drifted (v0.4.0-rc.1shipped to npm as1.0.0). Now derives the version from the git tag and keepspackage.jsonat a0.0.0placeholder, like qstash-cli.