chore(deps): update vulnerable dependencies - #13169

Reviewed 7f5b68a8fefb32761baa9e308c75ed4d4bfdca73. I found no new blocking dependency issues in this diff; merge readiness still depends on the current CI run.

The root production audit passes this PR’s stated high/critical threshold (#13078), but it does not supersede #10985, which targets the remaining findings in #10850. On this exact head, corepack pnpm audit --prod --audit-level high exits 0, with 0 high, 0 critical, 11 moderate and 2 low findings. Re-running at the low threshold confirms:

The original high-severity failure in #10850 was already cleared by #10862; the issue was explicitly left open for the remaining uuid finding. #10985 upgrades these two packages and migrates the diff types. That work still needs to be rebased onto the current pnpm tree and reviewed separately before closing #10850.

The nine changed files are byte-identical to the previously verified fa55110 snapshot, including the provider example's corrected undici floor. All six existing review threads are resolved. Previous lockfile/parity checks, the frozen lockfile validation, and the example build/typecheck/audit therefore remain applicable to those unchanged files.

The previous Java run failed the Flyway uniqueness check because two migrations used V31. At this head, the session-close migration is V32 and the exact CI uniqueness command passes (32 unique migrations). Full Java/database/E2E results still require the latest CI run; this static check alone does not establish that those jobs pass.
Latest CI snapshot: the pnpm worktree installs pass on Linux, macOS and Windows, and several Java jobs pass. The main Qwen Code CI and remaining Java/TUI checks are still queued or running. GitHub still reports CHANGES_REQUESTED; this comment is a scope/verification update, not an approval.

Follow-up review of the same head: two independent static passes found no new correctness or dependency-security issue. All five updated packages in the standalone agent-sdks lockfile have tarball URLs and integrity values matching the official npm registry. A source-level smoke check resolved the actual [email protected] and passed successful download/file-permission and byte-limit/partial-file-cleanup assertions. It used undici MockAgent and reused the other dependencies from the existing checkout; it did not exercise real DNS/TLS/proxy connections or replace the full package build/unit/CI checks. No new inline findings.

APPROVE · HEAD 7f5b68a8 · Scan tier

Security dependency update. Checked mechanical consistency across the 9 changed files.

What was verified

Every package.json specifier, pnpm-lock.yaml resolved version, and NOTICES.txt entry are internally consistent at this HEAD. The bot's prior R1-2 finding (NOTICES.txt recording versions inconsistent with the lockfile) is closed — [email protected] in NOTICES.txt matches the 7.30.0 resolution in pnpm-lock.yaml.

pnpm-workspace.yaml overrides for @grpc/grpc-js and brace-expansion@2 are set in both pnpm-workspace.yaml and package.json root overrides. The @a2a-js/sdk peer-dependency reference to @grpc/grpc-js is updated from 1.14.4 to 1.14.5 consistently across the lock file.

The cua-driver/examples/agent-sdks/package-lock.json bump to @hono/[email protected] is an example-subdirectory lockfile update and does not affect the main workspace.

No code changes. corepack pnpm audit --prod --audit-level high reported 0 high, 0 critical per the author's evidence (remaining moderate/low findings are tracked in #10985 and are outside this PR's stated scope).

Reviewed with AI assistance.

Reviewed at the current head. The bumps are consistent across the four manifests (undici ^7.29.1 floor everywhere), the lockfile resolves undici 7.30.0 / fast-uri 3.1.8 / @grpc/grpc-js 1.14.5 / brace-expansion 2.1.7, and NOTICES.txt now records exactly those — the round-2 ledger drift finding is closed. 0 unresolved threads; the three bot CRs were filed on superseded heads and are dismissed as stale. CI: 25 green, rest skipped/pending, nothing red. Not verified locally: no frozen-lockfile install or unit suites against undici 7.30.0 — registry integrity is enforced at install time by the lock hashes.