Repository navigation
fix(release): allow all major-zero editor versions - #551
Merged
Merged
Conversation
|
✅ Deploy Preview for stacks-editor ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
Allow the
v0branch to publish any valid semantic version with major version zero, including prereleases and build metadata. Continue rejecting invalid versions and major versions one or higher.Changes
0.15.xversions.legacy-v0npm dist-tag and existing release workflow unchanged.No package changeset is needed: this changes release validation and documentation, not the editor package. WebP support will be a separate PR.
How to test
Using Node 24 LTS:
npm ci.npm run test:release-config. All 8 tests should pass, including acceptance of0.16.0-beta.1and rejection of1.0.0,1.0.0-beta.1, and2.0.0.node scripts/validate-v0-version.mjs. The current package version should pass.npm run lintandnpx tsc --noEmit. Both should succeed.All checks above passed locally. Lint reported two existing assertion warnings in the stack-snippets tests. No package publication was attempted; GitHub CI is pending.