chore: freeze the whole Vite/SvelteKit toolchain majors in Dependabot#17
Merged
Merged
Conversation
Freezing only vite/typescript (#15) wasn't enough: PR #16 bumped @sveltejs/vite-plugin-svelte to ^7, which peer-requires vite ^8, while vite stays ^7 -> npm ERESOLVE (same class as #13/#7). The toolchain is coupled and must move in one coordinated upgrade (gated on node >=20.19 for vite 8). Ignore every toolchain major (vite, vitest, @sveltejs/*, svelte, svelte-check, typescript); minor/patch still flow, runtime deps unaffected.
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.
Why: freezing only
vite/typescript(#15) left siblings free to jump the vite generation. #16 bumped@sveltejs/vite-plugin-svelte→ ^7.2.0, which peer-requiresvite ^8while vite is pinned ^7 → npm ERESOLVE (same failure class as #13 and #7).Fix: the Vite/SvelteKit build+test toolchain is coupled and must upgrade together (as the manual vite 5→7 bump did). Ignore the major for every toolchain package —
vite,vitest,@sveltejs/*,svelte,svelte-check,typescript. Minor/patch bumps still flow; runtime deps (@noble/ed25519,qrcode) are untouched.To lift later: bump node to ≥20.19 (or 22 LTS) and do one coordinated upgrade to the vite-8 generation, then drop the relevant
ignoreentries.No product change. YAML validated locally.