deps: bump the vite-toolchain group across 1 directory with 3 updates - #91
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the vite-toolchain group with 3 updates in the /frontend directory: [@sveltejs/vite-plugin-svelte](https://github.com/sveltejs/vite-plugin-svelte/tree/HEAD/packages/vite-plugin-svelte), [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `@sveltejs/vite-plugin-svelte` from 7.3.0 to 7.3.1 - [Release notes](https://github.com/sveltejs/vite-plugin-svelte/releases) - [Changelog](https://github.com/sveltejs/vite-plugin-svelte/blob/main/packages/vite-plugin-svelte/CHANGELOG.md) - [Commits](https://github.com/sveltejs/vite-plugin-svelte/commits/@sveltejs/vite-plugin-svelte@7.3.1/packages/vite-plugin-svelte) Updates `vite` from 8.3.0 to 8.3.1 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v8.3.1/packages/vite) Updates `vitest` from 5.0.0 to 5.0.2 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.2/packages/vitest) --- updated-dependencies: - dependency-name: "@sveltejs/vite-plugin-svelte" dependency-version: 7.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vite-toolchain - dependency-name: vite dependency-version: 8.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vite-toolchain - dependency-name: vitest dependency-version: 5.0.2 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vite-toolchain ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
CherylSnowVeil
left a comment
CherylSnowVeil
left a comment
Collaborator
There was a problem hiding this comment.
Review — vite-toolchain group bump (vite 8.3.1, @sveltejs/vite-plugin-svelte 7.3.1, vitest 5.0.2)
Patch-level atomic bump of the three version-locked toolchain packages. I verified the full compatibility chain against the current lockfile rather than relying on version ranges alone:
- Atomicity: all three members of the
vite-toolchaindependabot group moved together — consistent with the documented requirement that these not be split (thesveltepackage itself is correctly not part of this group and stays at^5.57.0;typescriptstays^6,svelte-check^4.7.6,jsdom^30all untouched). - Peer chain: lockfile resolves to a single
vite@8.3.1, which satisfiesvite-plugin-svelte@7.3.1(vite ^8.0.0-beta.7 || ^8.0.0,svelte ^5.46.4),vitest@5.0.2(vite ^6.4.0 || ^7.0.0 || ^8.0.0), and@vitest/mocker@5.0.2(vite ^6||^7||^8). No nested/private vite install — the failure mode from the earlier isolated vite bump (PR #40) does not recur. - Lockfile consistency: root
devDependenciesinpackage-lock.jsonmatchpackage.jsonexactly;lockfileVersion3. Transitive moves are all driven by the bumped packages' own ranges:rolldown1.2.8→1.2.11 (vite'srolldown ~1.2.9dep),@oxc-project/types0.149→0.151 (rolldown's=0.151.0),magic-string/sourcemap-codecunder@vitest/mocker. Thesiginfo/stackbackremovals are clean — they were deps ofwhy-is-node-running@2.3.0, which vitest 5.0.2 replaced with the dependency-free^3.2.1(resolved 3.2.2). - Release content: all three are benign patch fixes.
vite-plugin-svelte7.3.1 is a pnpm-only inspector fix (repo uses npm — no impact). vite 8.3.1 is dep updates plus optimizer/mergeConfig/sourcemap fixes; vitest 5.0.1+5.0.2 are bug fixes. Nothing touches this repo's usage (vite buildx2,vitest runwith jsdom env,vitest/configdefineConfiginvite.config.ts— the standard co-location pattern, unaffected by vitest 5.0.1's import-resolution fix). - Recency: published 2026-09-23/24/25 — vitest 5.0.2 is ~6 days old, marginally under the informal 7-day settling preference, but that guideline targets newly-added dependencies; for a routine dependabot patch group with Snyk + dependency-review green this is acceptable. Worth noting only as context.
No actionable findings on the diff itself.
Two notes, neither blocking:
- 🟢 Dependabot flagged on this PR that the
npmlabel referenced independabot.ymldoesn't exist in the repo (labels: ["dependencies", "npm"]), so npm-ecosystem PRs won't get labeled until it's created or the label list is trimmed. Pre-existing config gap, unrelated to this diff. - ℹ️ The
testcheck (make testin the pinned container — the realnpm ci+vitest run+svelte-checkverification) was still in progress at review time; Snyk, zizmor, and dependency-review are already green. Merge should wait ontestas usual.
Summary: Correctly-scoped atomic toolchain bump with a consistent lockfile and satisfied peer chain. Safe to merge once the test job goes green.
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.
Bumps the vite-toolchain group with 3 updates in the /frontend directory: @sveltejs/vite-plugin-svelte, vite and vitest.
Updates
@sveltejs/vite-plugin-sveltefrom 7.3.0 to 7.3.1Release notes
Sourced from @sveltejs/vite-plugin-svelte's releases.
Changelog
Sourced from @sveltejs/vite-plugin-svelte's changelog.
Commits
54c6efeVersion Packages (#1398)8d032b2fix(inspector): activate under Vite+ on pnpm by matching the realpathed clien...Updates
vitefrom 8.3.0 to 8.3.1Release notes
Sourced from vite's releases.
Changelog
Sourced from vite's changelog.
Commits
39ddf7crelease: v8.3.1 (#23573)f68c0d5fix: handleserver.ws: falsein mergeConfig (#23511)6f831f9fix(server): avoid reinitializing watcher when adding file after server close...04fc30afix(sourcemap): skip URL source roots when injecting sources content (#23519)5f89433fix(optimizer): resolve pending discovered dep processing on close before ini...63567c7chore(optimizer): add debug log when waiting for dep before init (#23566)e8990c4fix(deps): update all non-major dependencies (#23537)af7cdf6refactor: replacefindwithsome(#23554)39330f4fix(optimizer): don't skip imports whose binding starts with type (#23540)9abd99brefactor: remove duplicate configurations (#23532)Updates
vitestfrom 5.0.0 to 5.0.2Release notes
Sourced from vitest's releases.
... (truncated)
Commits
428e2e5chore: release v5.0.2 (#11357)0b79231fix: bindprocessin case global is overwritten (#11343)597df56docs: correct stale config defaults (#11354)ea1c44fdocs:sequence.setupFilesdefault is'list'(#11351)0fd6b97fix(detect-async-leaks): ignoreprocess.stdiohandles (#11333)4e91e56fix(reporters):hanging-processto use ESM entrypoint (#11316)1a57929docs(browser): fix locators.exact default (#11338)5b95efbfix(reporter):agentto respect--silent(#11271)f58a209docs: correct benchmark.exclude and watch defaults (#11268)d1c3eccfix(jsdom): fixRequestwithBlobbody on jsdom 28+ (#11295)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions