chore(deps): bundle the four open npm Dependabot PRs - #490
Merged
Merged
Conversation
Supersedes #486, #487, #488, #489 in one branch, one lockfile regeneration, one CI run. Production (#486): @codemirror/commands 6.11.0 -> 6.11.1, @codemirror/state 6.7.4 -> 6.7.6, @codemirror/view 6.43.11 -> 6.43.13, lucide-react 1.46.0 -> 1.47.0. Development: @types/node 22.20.0 -> 22.20.4 and jsdom 30.0.1 -> 30.1.1 (#487), @vitejs/plugin-react 5.2.0 -> 6.1.1 (#488), vitest 4.1.11 -> 5.0.1 (#489). **Why:** every npm Dependabot PR here regenerates pnpm-lock.yaml without honouring package.json's pnpm.overrides, which drops the 15-key security block and fails CI at install. Merging them serially also conflicts each remaining lockfile in turn. So the specifiers are edited by hand, the lockfile is reset to main's and regenerated once, and the importers are diffed against main to confirm only the intended entries moved. @babel/core now resolves NOWHERE: @vitejs/plugin-react 6 dropped the babel transform, taking the whole subtree out. Its override key and advisory floor are deliberately kept — they cost nothing while the package is absent and are what catches it arriving again by another route, exactly as the ip-address entry already does. Verified: pnpm test 4184 passed (408 files), tsc --noEmit and the e2e tsconfig both clean, vite build succeeds, pnpm audit reports no known vulnerabilities, and pnpm tauri info shows no npm/crate version-pair mismatch. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This was referenced Sep 22, 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.
Bundles the four open npm Dependabot PRs into one branch, one lockfile regeneration, one CI run.
Supersedes #486, #487, #488, #489.
@codemirror/commands@codemirror/state@codemirror/viewlucide-react@types/nodejsdom@vitejs/plugin-reactvitestWhy one PR instead of four merges
Every npm Dependabot PR here regenerates
pnpm-lock.yamlwithout honouringpackage.json'spnpm.overrides, dropping the 15-key security block and failing CI atpnpm install --frozen-lockfile. Merging them serially also flips each remaining lockfile toCONFLICTINGin turn. So: specifiers edited by hand, lockfile reset tomain's and regenerated once, importers diffed againstmainto confirm only the intended entries moved. The overrides block is untouched andtest/depOverrides.test.tspasses.@types/nodestays on the^22specifier — it tracks the Node 22 toolchain and is ignored at semver-major by design; only the patch moved.One thing worth a reviewer's eye
@babel/corenow resolves nowhere in the lockfile:@vitejs/plugin-react6 dropped the babel transform and the whole subtree left. Its override key and advisory floor are deliberately kept, not deleted — they cost nothing while the package is absent and are what catches it arriving again by another route, exactly as the existingip-addressentry already does.test/depOverrides.test.tspasses vacuously for it, which is the documented behaviour for an absent package.Verification
pnpm test— 4184 passed (408 files), includingdepOverridesand the doc invariantspnpm tsc --noEmit— cleanpnpm exec tsc -p e2e/tsconfig.json --noEmit— cleanpnpm vite build— succeedspnpm audit— no known vulnerabilitiespnpm tauri info— no npm/crate version-pair mismatchTwo semver-major dev bumps (
vitest4 to 5,@vitejs/plugin-react5 to 6) are covered by the suite and the build above; no test or source change was needed for either.🤖 Generated with Claude Code