Skip to content

fix(release): use valid V2 npm dist-tag - #2375

Open
dancormier wants to merge 1 commit into
v2from
STACKS-846/fix-legacy-v2-dist-tag
Open

fix(release): use valid V2 npm dist-tag#2375
dancormier wants to merge 1 commit into
v2from
STACKS-846/fix-legacy-v2-dist-tag

Conversation

@dancormier

Copy link
Copy Markdown
Contributor

Summary

  • replace the invalid v2 npm dist-tag with legacy-v2
  • validate the release tag before publishing
  • add CI coverage preventing SemVer-like dist-tags
  • document the V2 maintenance release tag

npm rejects v2 because it parses as a semantic-version range. Without this correction, future V2 releases would fail during publication.

Testing

Automated and local verification:

  • npm ci
  • npm run test:release-config
  • npm run build
  • npm run lint
  • npx eslint scripts
  • focused formatting checks

Material reviewer checks that do not publish packages:

  1. Run node scripts/validate-npm-dist-tag.mjs legacy-v2 and confirm it exits successfully.
  2. Run node scripts/validate-npm-dist-tag.mjs v2 and confirm it exits non-zero with an invalid or SemVer-like tag error.
  3. Inspect package.json and confirm release:v2 validates and publishes the same single legacy-v2 tag.
  4. Inspect the CI matrix and confirm Release Config Tests runs before any future V2 release can pass CI.

Do not run npm run release:v2 during review; it is the real package publication command.

After this PR merges, adding legacy-v2 to the already-published Classic 2.9.0 and Svelte 0.7.0 packages will be handled as a separately approved npm registry mutation. Verification will confirm that legacy-v2 resolves to those versions while latest remains unchanged.

Jira

STACKS-846

@changeset-bot

changeset-bot Bot commented Aug 18, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 34fc785

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@netlify

netlify Bot commented Aug 18, 2026

Copy link
Copy Markdown

Deploy Preview for stacks ready!

Name Link
🔨 Latest commit 34fc785
🔍 Latest deploy log https://app.netlify.com/projects/stacks/deploys/6a84e114d4295c0008945f11
😎 Deploy Preview https://deploy-preview-2375--stacks.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@dancormier
dancormier marked this pull request as ready for review August 18, 2026 22:51
@dancormier
dancormier requested a review from a team as a code owner August 18, 2026 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant