Skip to content

chore(deps): bump TS SDK dev deps to clear security advisories - #104

Merged
prashar32 merged 1 commit into
mainfrom
chore/ts-sdk-dep-bumps
Jun 12, 2026
Merged

chore(deps): bump TS SDK dev deps to clear security advisories#104
prashar32 merged 1 commit into
mainfrom
chore/ts-sdk-dep-bumps

Conversation

@prashar32

Copy link
Copy Markdown
Owner

Clears all three open Dependabot advisories on the TypeScript SDK in one pass, with a passing test suite.

package advisory was now
vitest critical (no 2.x patch) 2.1.9 3.2.6
vite medium 5.4.21 7.3.5 (transitive)
esbuild medium 0.21.5 0.25.12 (override)

npm audit reports 0 vulnerabilities.

Why one PR instead of the two bot PRs

The critical advisory is on vitest itself and is only fixed in 3.2.6 — there's no 2.x patch, so we can't override our way out. vitest 3 imports util.styleText, which Node 18 lacks, so both bot PRs (#100, #102) failed CI on the Node 18 job. This PR makes the matching support call:

  • test matrix → Node 20 & 22;
  • package engines floor → >=20.

Node 18 is EOL (April 2025), the runtime only needs fetch, and the package isn't published to npm yet (#82), so no supported consumer is dropped. An esbuild override pins ≥0.25 across the whole tree (it's pulled by both vitest/vite and tsup).

Closes #100. Closes #102.

Bump vitest to ^3.2.6 (the version that closes the critical advisory; there is
no 2.x patch), and force esbuild to ^0.25.0 via an override so every copy in the
tree — under both vitest/vite and tsup — is on a patched release. vite resolves
to 7.x transitively. `npm audit` is now clean.

vitest 3 requires Node 20.12+ (it imports `util.styleText`), so the test matrix
moves to Node 20 and 22 and the package engines floor is raised to >=20. Node 18
is EOL, the runtime itself only needs `fetch`, and the package isn't on npm yet,
so this drops no supported consumer.

Supersedes the split Dependabot PRs (#100, #102), which each bumped a subset and
failed CI on Node 18.
@prashar32
prashar32 merged commit 25aec2e into main Jun 12, 2026
7 checks passed
@prashar32 prashar32 mentioned this pull request Jun 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant