Repository navigation
chore(deps): batch trivial dependency updates (2026-09) - #511
Merged
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Batch-applies the open Renovate/Dependabot updates that need no substantive source
changes, re-derived on top of current
main(the perf-fixture bot PRs were openedagainst the pre-#497 lockfile) and verified locally against the full CI suite. Each
update was triaged individually rather than per-PR, so mixed group PRs are split.
Same approach as #474.
Included updates
Root (
package.json/package-lock.json)oxlint1.77.0→1.81.0dompurify(override)3.4.13→3.4.15@jupyter-widgets/base6.0.11→6.0.12(lockfile only)@jupyter-widgets/controls5.0.12→5.0.13(lockfile only)@types/*(lockfile only, 25 packages)chai-arrays2.0.3,chai-as-promised7.1.8,cors2.8.19,debug4.1.13,dedent0.7.2,del4.0.3,format-util1.0.4,glob5.0.38,json2csv5.0.7,loadable__component5.13.10,lodash4.17.25,node-fetch2.6.13,promisify-node0.4.3,react-dom16.9.25,react-redux7.1.34,react-virtualized9.22.3,redux-logger3.0.13,sinon10.0.20,strip-comments2.0.4,svg-to-pdfkit0.1.4,tcp-port-used1.0.4,tmp0.2.6,url-parse1.4.11,vscode-notebook-renderer1.72.4Perf fixture (
src/test/vscode-notebook-perf/)@vscode/test-cli^0.0.8→^0.0.15glob^7.1.2→^13.0.6Neither package is imported by the fixture's two source files (
src/api.ts,src/extension.ts), so theglobmajor has no API surface to break;npm installand
npm run compileboth succeed.Test venv requirements (
build/venv-test-ipywidgets8-requirements.txt)pillow>=10.2.0→>=12.3.0zipp>=3.19.1→>=4.1.0jupyter-server>=2.14.1→>=2.21.0tornado>=6.5→>=6.5.8urllib3>=2.2.2→>=2.7.0No workflow in
.github/workflows/currently installs this file (the only Pythonsetup is in
e2e.yml, which runsnpm cionly), so it cannot break CI. Resolutionwas verified locally instead:
uv pip compile --python-version 3.12resolves boththe current and the bumped file, and each bumped lower bound is the current latest
release.
Supporting changes
overridesgainsmocha → diff 5.2.2, copied from the rootpackage.json.@vscode/test-cli0.0.15 nestsmocha11.8.0, which depends ondiff ^7.0.0;diff@7.0.0is vulnerable to GHSA-73rr-hh4g-fpgx and theqlty check --all --filter=osv-scannergate that fix(ci): refresh perf-fixture lockfile and gate it with osv-scanner #497 turned on fails on it(verified: 1 medium finding without the override,
No issueswith it). This isthe same mechanism fix(ci): refresh perf-fixture lockfile and gate it with osv-scanner #497 used for
serialize-javascript.mocha11.8 /c811 /yargs18 treeunder
@vscode/test-cli. This matches what chore(deps-dev): bump @vscode/test-cli from 0.0.8 to 0.0.15 in /src/test/vscode-notebook-perf #505 itself produces; the top-levelmochastays at 10.8.2.npm installforthe two
package.jsonedits,npm update <pkg>...for the lockfile-only bumps),not blanket-regenerated.
typescriptstays at 5.8.3,@types/nodeat 22.15.31.Excluded (needs its own PR)
mocha11.0.1→11.8.011.0.1— 11.8 loads the--requirebootstrap as ESM and kills the unit suite (see #474).@types/node22.15.31→22.20.xsrc/platform/common/process/proc.node.ts(NonSharedBuffernot assignable tostring). Needs source changes.@types/chai4.3.6→4.3.20assert.isOk<T>insrc/test/datascience/notebook/helper.tsnowTS2558(no type args), and an assertion-narrowing change makesfederatedAuthSqlBlockCodeGenerator.node.unit.test.ts:348anever. Needs source changes.@types/node18.19.130→26.4.1.nvmrcis 22.mocha10.8.2→12.0.0typescript5.9.3→7.0.2uuid13.0.2→14.0.0.nvmrc)@nteract/transform-vega→7.0.10@blueprintjs/core3.54 and fails both audit jobs; not re-verified here.react-svgmt1.1.11→1.2.0ERESOLVE: peerreact@^17, repo is onreact@16.Supersedes
Renovate and Dependabot close their own PRs automatically once the dependency is at
the target version on
main, so after this merges these should close on their own:@types/node,@types/chairemain), chore(deps): update devdependencies #289 (
mocharemains)Already satisfied by
mainbefore this PR and closed separately: #417(
@vscode/extension-telemetry1.5.2 via #469), #494 (fixture nestedglob10.5.0via #497), #495 (
js-yaml4.3.2 via #498), #496 (morgan1.12.0 via #498).Verification
Run locally in a worktree on Node 22.21.1 / npm 10.9.4. Root install used
npm ci --ignore-scripts+npm run postinstallbecausezeromqold(zeromq6.0.0-beta.6) has no darwin-arm64 prebuild and this machine has no
cmake; that isa local-environment limitation unrelated to anything in this PR.
tsc -p ./(compile-tsc)npm run typechecknpm run test:unittestsnpm run lintno-unused-varswarnings — identical count under oxlint 1.77.0 and 1.81.0)npm run formatnpm run spell-checknpm run check-licensesnpm audit --omit=devnpx tsx build/esbuild/build.tsnpm install --package-lock-onlyidempotency (drift check)npm install+npm run compilenpm auditqlty check --all --filter=osv-scanner(qlty 0.643.0)No issuesuv pip compile --python-version 3.12 build/venv-test-ipywidgets8-requirements.txtnpm audit(including dev) still reports the same 5 low-severity findings asmain(
ellipticviabrowserify-sign/create-ecdh/crypto-browserify/node-stdlib-browser);those are not introduced here.
🤖 Generated with Claude Code
Summary by CodeRabbit