Skip to content

fix(sv): community add-on template pins sv and @sveltejs/sv-utils versions#1108

Merged
jycouet merged 1 commit into
mainfrom
sv-peer-dependency-can-t-be-latest
May 31, 2026
Merged

fix(sv): community add-on template pins sv and @sveltejs/sv-utils versions#1108
jycouet merged 1 commit into
mainfrom
sv-peer-dependency-can-t-be-latest

Conversation

@jycouet
Copy link
Copy Markdown
Contributor

@jycouet jycouet commented May 29, 2026

Closes #1102

The addon template was generating package.json with "sv": "latest" in peerDependencies, which pnpm warns about (peer ranges should be real version ranges).

The build script now reads the current sv and @sveltejs/sv-utils versions from the workspace and substitutes ^<version> for workspace:* in package.template.json.

Tests normalize these versions before snapshot comparison so the snapshot doesn't drift on every release.

…ils` to a version range instead of `latest`
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 29, 2026

🦋 Changeset detected

Latest commit: 7f0fd82

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
sv Patch

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

@jycouet jycouet merged commit 0f28fb4 into main May 31, 2026
5 of 6 checks passed
@jycouet jycouet deleted the sv-peer-dependency-can-t-be-latest branch May 31, 2026 14:00
@github-actions github-actions Bot mentioned this pull request May 31, 2026
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.

sv peer dependency can't be latest

1 participant