fix(ci): sync npm version from git tag at publish time - #22
Merged
Conversation
Instead of requiring manual version bumps, the publish workflow now reads the version from the release tag (vX.Y.Z) and updates package.json before publishing. Same approach as tradingview-mcp.
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.
Problem
The publish workflow reads the version from
package.json, which was still0.1.0when thev0.2.0release was created. npm refused to publish because0.1.0already exists.Fix
Read the version from the git tag (e.g.
v0.2.0) and sync it intopackage.jsonat publish time vianpm version --no-git-tag-version. Same dynamic version approach used in tradingview-mcp.After merge
Move the existing
v0.2.0tag to the merge commit so the publish workflow picks it up: