Skip to content

Fix failing Dependabot security updates in lang/typescript - #679

Closed
DominiqueFlaaa wants to merge 1 commit into
mainfrom
fix-dependabot-security-updates
Closed

DominiqueFlaaa wants to merge 1 commit into
mainfrom
fix-dependabot-security-updates

Conversation

@DominiqueFlaaa

Copy link
Copy Markdown
Contributor

What are you trying to accomplish?

Two Dependabot security update jobs fail on main:

vitest@^3 pins tinypool@1.x, so Dependabot cannot reach the fixed version on its own.

What approach did you choose and why?

In lang/typescript only (dev dependencies; nothing in the published package changes):

  • vitest ^3.0.0 → ^4.1.12. Vitest 4 no longer depends on tinypool, and 4.1.12 fixes @vitest/mocker (GHSA-qxg6-89mg-rqv8). The existing vitest.config.ts works unchanged.
  • vite override ^6.4.2 → ^6.4.4 (resolves to 6.4.6), for GHSA-9jrq-w75r-8gcw and the launch-editor advisories.
  • New source-map-js override ^1.2.2, following the existing overrides.

pnpm 9.1.3 does not apply overrides to the vite peer it auto-installs for vitest; it kept the 6.4.3 lockfile entry. I removed the vite@6.4.3 entries and let pnpm resolve them again. The lockfile resolves from registry.npmjs.org.

What should reviewers focus on?

The vitest major bump. The test suite passes without config changes.

The impact of these changes

Dev tooling only. No change to the Ruby gem or the published npm package.

Testing

With pnpm 9.1.3 in lang/typescript, the same steps as CI Typescript: pnpm install --frozen-lockfile, pnpm typecheck, pnpm lint, pnpm test (7 files, 162 tests passed), pnpm build.

Checklist

  • I have added a CHANGELOG entry for this change (or determined that it isn't needed)

Dependabot could not resolve the security updates for tinypool and
source-map-js: vitest 3 pins tinypool 1.x, and the fixed versions are
2.1.2 and 1.2.2. Move vitest to ^4.1.12, which no longer depends on
tinypool and also fixes @vitest/mocker (GHSA-qxg6-89mg-rqv8).

Raise the vite override to ^6.4.4 (GHSA-9jrq-w75r-8gcw and related
launch-editor advisories) and add a source-map-js ^1.2.2 override
(GHSA-68fv-2mgg-jv7q). The vite peer that pnpm installs for vitest kept
the old lockfile entry, so the lockfile entries for vite were resolved
again.
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