ci(release): use --tag next for prereleases#10
Merged
Conversation
Modern npm rejects publishing prerelease versions without an explicit --tag, because tagging an `x.y.z-alpha.N` as `latest` would break `npm install themeparks` for existing users. Parse the version from the git tag and pick the dist-tag accordingly: - Prerelease (contains a "-") -> --tag next - Stable release -> default (latest) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the npm release GitHub Action to publish prerelease versions under a non-latest dist-tag, matching modern npm’s expectation that prereleases use an explicit tag.
Changes:
- Adds a
Publishstep that derives the version from the pushed git tag (GITHUB_REF_NAME). - Publishes prereleases (versions containing
-) withnpm publish --tag next; otherwise publishes normally (defaultlatest).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Modern npm requires prereleases to use an explicit dist-tag. Parse the git-tag version and pick next/latest accordingly.