Skip to content

chore(deps): vitest 3.2.7 in every workspace - #43

Merged
alejoamiras merged 1 commit into
mainfrom
deps/vitest-3.2.7
Nov 18, 2026
Merged

alejoamiras merged 1 commit into
mainfrom
deps/vitest-3.2.7

Conversation

@alejoamiras

Copy link
Copy Markdown
Collaborator

What changes

Workspace Before After
services/auth, packages/contract-verification 0.34.6 3.2.7
services/explorer-api, services/explorer-ui-v2, services/websocket-event-publisher, packages/message-registry, packages/redis-helper, packages/test-harness 3.2.4 3.2.7
services/aztec-listener ^3.2.4 ^3.2.7
  • vitest is a devDependency everywhere, so no production image changes.
  • packages/contract-verification/vitest.config.ts: threads: false is a 0.34 option that 3.x no longer accepts (the type check fails on it). It becomes pool: "forks", which keeps that package's tests in child processes, as the comment there requires.
  • No test file changes.
  • The lockfile now holds a single vitest, 3.2.7, and its @vitest/* 3.2.7 packages. The 0.34.6 chain and the 3.2.4 packages leave: 8 packages come in and 45 leave. All 8 are older than 7 days.

Advisories

A simulation against the open alert list predicts 9 closures, all critical GHSA-5xrq-8626-4rwp: one on each of the eight exact-pinned manifests above, and one on yarn.lock. aztec-listener's range had no alert of its own.

What stays open, or opens:

  • GHSA-82fw-gwwq-j7x9 (medium) is fixed only in vitest 4.1.11, and 3.2.7 is inside its range.
    • It stays open on yarn.lock and on the seven manifests that already declared 3.x.
    • It will likely open on services/auth and packages/contract-verification, whose 0.34.6 was below its range.
  • @vitest/mocker GHSA-qxg6-89mg-rqv8 (medium, fixed in 4.1.12), and tinypool 1.1.1's two advisories (fixed in 2.1.1 and 2.1.2), on yarn.lock. vitest 3.x depends on tinypool ^1.1.1.

Local gates

Gate Result
yarn install --immutable pass; the same peer warnings as the base
yarn build:packages && yarn build pass
yarn lint, then git diff --exit-code pass, no changes
yarn test pass: 252 tests, the same as the base, none skipped
Test names the same tests pass before and after (compared on an earlier base with 247 tests)
yarn test:integration pass: 31 tests; no harness project left behind

To compare test names, every workspace's suite ran with the JSON reporter before and after. Two differences are normalized away:

  • vitest 0.34's reporter prefixes each full test name with a space;
  • auth's isUUID failure tests carry a random suffix in their names, so they differ between any two runs.

🤖 Generated with Claude Code

Every workspace that runs vitest now declares 3.2.7: auth and contract-verification move from
0.34.6, the others from 3.2.4, and aztec-listener's range becomes ^3.2.7. The lockfile keeps one
vitest and drops the 0.34.6 chain.

contract-verification's config replaced the 0.34-only `threads: false` with `pool: "forks"`,
which keeps its tests in child processes. No test file changes; every workspace runs the same
tests as before, all passing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@alejoamiras
alejoamiras merged commit 00cb5c9 into main Nov 18, 2026
24 checks passed
@alejoamiras
alejoamiras deleted the deps/vitest-3.2.7 branch November 18, 2026 16:40
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