Version Packages - #443
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dferber90
enabled auto-merge (squash)
July 24, 2026 15:04
dferber90
approved these changes
Jul 24, 2026
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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
flags@4.2.3
Patch Changes
622d56eThanks @dferber90! - Remove@sveltejs/kitfrom peer dependencies. It was declared as an optional peer with a"*"range, which caused npm to auto-install the newest@sveltejs/kitand drag in its transitive@sveltejs/vite-plugin-svelte→vitepeer chain. In non-SvelteKit projects already on Vite 7 (via Vitest, Storybook, etc.) this produced a hardERESOLVEerror requiringnpm install --force. SvelteKit consumers always have@sveltejs/kitinstalled as the framework, so theflags/sveltekitentrypoint continues to resolve it from their own tree.