fix(release): use valid V2 npm dist-tag - #2375
Open
dancormier wants to merge 1 commit into
Open
Conversation
|
✅ Deploy Preview for stacks ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
dancormier
marked this pull request as ready for review
August 18, 2026 22:51
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.
Summary
v2npm dist-tag withlegacy-v2npm rejects
v2because it parses as a semantic-version range. Without this correction, future V2 releases would fail during publication.Testing
Automated and local verification:
npm cinpm run test:release-confignpm run buildnpm run lintnpx eslint scriptsMaterial reviewer checks that do not publish packages:
node scripts/validate-npm-dist-tag.mjs legacy-v2and confirm it exits successfully.node scripts/validate-npm-dist-tag.mjs v2and confirm it exits non-zero with an invalid or SemVer-like tag error.package.jsonand confirmrelease:v2validates and publishes the same singlelegacy-v2tag.Release Config Testsruns before any future V2 release can pass CI.Do not run
npm run release:v2during review; it is the real package publication command.After this PR merges, adding
legacy-v2to the already-published Classic2.9.0and Svelte0.7.0packages will be handled as a separately approved npm registry mutation. Verification will confirm thatlegacy-v2resolves to those versions whilelatestremains unchanged.Jira
STACKS-846