chore(deps): bump vitest, brace-expansion, pypdf and tornado

[yuneng-berri]

Relevant issues

None

Linear ticket

None

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have added meaningful tests (lockfile-only bump; covered by the existing 3943-test dashboard vitest suite, run locally against the bumped versions)
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

Screenshots / Proof of Fix

osv-scanner against the dashboard lockfile before the bump:

$ osv-scanner scan source -L ui/litellm-dashboard/package-lock.json
| https://osv.dev/GHSA-jxxr-4gwj-5jf2 | 6.5 | npm | brace-expansion (dev) | 5.0.5 | 5.0.6 | ui/litellm-dashboard/package-lock.json |
| https://osv.dev/GHSA-5xrq-8626-4rwp | 9.8 | npm | vitest (dev)          | 3.2.4 | 3.2.6 | ui/litellm-dashboard/package-lock.json |

After the bump, both entries are gone. Dashboard test suite on vitest 3.2.6:

$ cd ui/litellm-dashboard && npx vitest run
Test Files  392 passed (392)
     Tests  3943 passed (3943)

Type

🚄 Infrastructure

Changes

Also bumps pypdf 6.10.2 to 6.13.1 and tornado 6.5.5 to 6.5.7 in uv.lock, clearing the advisories published for both after this branch was opened.

Regression guards: the pypdf floor is raised to >=6.12.0 in pyproject (direct dependency, so the minimum applies to package consumers as well), and [tool.uv] constraint-dependencies pins the transitive/test-blocked versions for this repo's resolution only: tornado >= 6.5.6, aiohttp >= 3.13.5 and < 3.14 (the ceiling holds until a vcrpy release supports aiohttp 3.14). A committed lockfile can no longer silently resolve below the bumped versions; each out-of-range uv lock -P attempt fails to resolve (verified for pypdf 6.10.2, tornado 6.5.5, aiohttp 3.13.3 and 3.14.1). Note this commit touches pyproject.toml.

Bumps the dashboard devDependencies vitest, @vitest/coverage-v8 and @vitest/ui from 3.2.4 to 3.2.6 (the three are peer-locked to each other, so they move together) and the transitive brace-expansion from 5.0.5 to 5.0.6. This clears both advisories currently published on osv.dev for the dashboard lockfile.

History note: this PR originally also bumped aiohttp 3.13.5 to 3.14.1 (plus a pyproject floor raise). That part is reverted on this branch and aiohttp stays at 3.13.5: vcrpy's aiohttp stubs import a symbol that aiohttp removed in 3.14, which breaks every cassette-based test suite, and the upstream vcrpy fix (kevin1024/vcrpy#996, merged 2026-06-09) has no release yet. The aiohttp bump should be redone once a vcrpy release newer than 8.1.1 ships. Verified after the revert: uv lock --check passes, aiohttp resolves to 3.13.5, vcr.stubs.aiohttp_stubs imports again, and the 154 tests/test_litellm/llms/custom_httpx/ tests pass

[yuneng-berri]

@greptileai

[greptile-apps]

Greptile Summary

Security-only dependency bump that clears four published advisories: vitest 3.2.4→3.2.6 (GHSA-5xrq-8626-4rwp, CVSS 9.8), brace-expansion 5.0.5→5.0.6 (GHSA-jxxr-4gwj-5jf2, CVSS 6.5), pypdf 6.10.2→6.13.1, and tornado 6.5.5→6.5.7.

• pyproject.toml: pypdf minimum raised to >=6.12.0 (affects package consumers) and [tool.uv] constraint-dependencies added to lock tornado and aiohttp floors so uv lock cannot silently resolve to a vulnerable version.
• ui/litellm-dashboard/package.json + package-lock.json: vitest peer-group and brace-expansion updated; all 3943 dashboard tests confirmed passing on the new versions per the PR description.
• uv.lock: Python lockfile re-resolved to the patched package versions; aiohttp intentionally stays at 3.13.5 pending a vcrpy release that supports aiohttp 3.14.

Confidence Score: 5/5

Lockfile-only changes patching four known vulnerabilities; no production logic is touched.

All changes are confined to package manifests and lockfiles. The bumped versions are patch/minor releases within already-declared version ranges, the full dashboard test suite passes on the new vitest version, and the PR documents both before/after osv-scanner output and the deliberate aiohttp revert with its reasoning.

No files require special attention.

Important Files Changed

Filename	Overview
pyproject.toml	Raises pypdf floor from >=6.10.2 to >=6.12.0 in proxy-runtime extras and adds uv constraint-dependencies pinning tornado>=6.5.6 and aiohttp>=3.13.5,<3.14 to prevent silent resolution below the patched versions.
ui/litellm-dashboard/package.json	Bumps vitest, @vitest/coverage-v8, and @vitest/ui from 3.2.4 to 3.2.6 to clear GHSA-5xrq-8626-4rwp (CVSS 9.8).
ui/litellm-dashboard/package-lock.json	Lockfile updated to reflect vitest 3.2.6 and brace-expansion 5.0.6, clearing both osv.dev advisories present in the prior lockfile.
uv.lock	Python lockfile updated to resolve pypdf 6.13.1 (from 6.10.2) and tornado 6.5.7 (from 6.5.5); aiohttp remains at 3.13.5 per the intentional revert documented in the PR description.

_{Reviews (3): Last reviewed commit: "chore(deps): add regression guards for t..." | Re-trigger Greptile}

[greptile-apps]

Greptile Summary

This PR bumps aiohttp from 3.13.5 to 3.14.1 in uv.lock (clearing two published CVEs) and updates vitest, @vitest/coverage-v8, and @vitest/ui from 3.2.4 to 3.2.6 in package.json/package-lock.json (clearing one critical-severity and one medium-severity advisory). No pyproject constraint or production source code was modified.

• uv.lock: Aiohttp 3.14.1 wheel hashes replace 3.13.5; a new typing-extensions entry appears in aiohttp's own dependency metadata for Python < 3.13, which is expected from upstream and is already a transitive dependency of the project.
• package.json / package-lock.json: Vitest ecosystem packages (including transitive @rollup/* 4.60.3 → 4.61.1 and brace-expansion 5.0.5 → 5.0.6) are updated to align with the new vitest release; all are devDependencies with no effect on the production bundle.

Confidence Score: 5/5

Safe to merge — all changes are confined to lockfiles and devDependency version pins, with no production source code touched.

Every changed file is either a lockfile (uv.lock, package-lock.json) or a devDependency version pin (package.json). The aiohttp bump is lock-only; the pyproject constraint is untouched. Vitest and its peers are build/test tools that do not enter the production bundle. The PR includes OSV scanner output confirming the targeted advisories are cleared, a live proxy smoke test against the bumped aiohttp, and passing unit/vitest runs — all of which give good confidence the bump is behaviorally inert.

No files require special attention.

Important Files Changed

Filename	Overview
uv.lock	Aiohttp bumped from 3.13.5 to 3.14.1; only wheel URLs/hashes and a new upstream typing-extensions marker changed — no other packages altered.
ui/litellm-dashboard/package.json	Pinned devDependency versions for vitest, @vitest/coverage-v8, and @vitest/ui updated from 3.2.4 to 3.2.6.
ui/litellm-dashboard/package-lock.json	Lockfile updated to reflect vitest 3.2.6 ecosystem; transitive @rollup/* packages bumped to 4.61.1 and brace-expansion to 5.0.6 — all devDependencies, no production bundle impact.

_{Reviews (2): Last reviewed commit: "chore(deps): bump aiohttp to 3.14.1 and ..." | Re-trigger Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

i revoke

[yuneng-berri]

@greptile