Repository navigation
fix(svelte): prepare 1.0.1 stable release - #2379
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 09ba167 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for stackoverflow-email ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for stacks 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
Context
The V2 release workflow accidentally published
@stackoverflow/stacks-svelte@1.0.0on June 24, 2026. That version was later unpublished, and npm permanently prevents it from being reused.Classic 3.0.0 and Utils 1.0.0 have published successfully. Svelte must advance to 1.0.1 to complete the stable release train.
Historical workflow: https://github.com/StackExchange/Stacks/actions/runs/28087530420
Verification
npm cinpx changeset status— Svelte patch onlynpm run test:release— 5 passedJira
STACKS-846