Derive npm dist-tag from package major in publish workflow - #79
Open
vigneshwerv wants to merge 1 commit into
Open
Derive npm dist-tag from package major in publish workflow#79vigneshwerv wants to merge 1 commit into
vigneshwerv wants to merge 1 commit into
Conversation
publish.yml ran a bare `npm publish`, which always moves the 'latest' dist-tag to whatever version is being published. That is wrong for maintenance releases on an older major: publishing 1.5.1 would have pointed 'latest' at it and pulled every `npm install @fragment-dev/node-client` back to the v1 line. Compare the package major against the current 'latest' major and publish older majors under a 'v<major>' tag instead.
sophieleewu
approved these changes
Aug 26, 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.
publish.ymlran a barenpm publish, which always moves thelatestdist-tag to whatever version is being published.That is wrong for maintenance releases on an older major: publishing
1.5.1from the v1 line would pointlatestat it, pulling everynpm install @fragment-dev/node-clientback from 2.1.0 to 1.5.1.This compares the package major against the current
latestmajor and publishes older majors under av<major>tag instead.Verified against the live registry:
v1latestlatestNeeded by the pending v1.5.1 backport release (branch
release/v1.5.1).