Repository navigation
chore(deps): vitest 3.2.7 in every workspace - #43
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
services/auth,packages/contract-verificationservices/explorer-api,services/explorer-ui-v2,services/websocket-event-publisher,packages/message-registry,packages/redis-helper,packages/test-harnessservices/aztec-listener^3.2.4^3.2.7packages/contract-verification/vitest.config.ts:threads: falseis a 0.34 option that 3.x no longer accepts (the type check fails on it). It becomespool: "forks", which keeps that package's tests in child processes, as the comment there requires.@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:
yarn.lockand on the seven manifests that already declared 3.x.services/authandpackages/contract-verification, whose 0.34.6 was below its range.@vitest/mockerGHSA-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), onyarn.lock. vitest 3.x depends on tinypool^1.1.1.Local gates
yarn install --immutableyarn build:packages && yarn buildyarn lint, thengit diff --exit-codeyarn testyarn test:integrationTo compare test names, every workspace's suite ran with the JSON reporter before and after. Two differences are normalized away:
isUUID failuretests carry a random suffix in their names, so they differ between any two runs.🤖 Generated with Claude Code