Repository navigation
chore: upgrade vitest to 3.2.7 and re-review the advisory table - #8
Merged
Merged
Conversation
Vitest 3 runs the existing config and API unchanged (86 tests, lint, typecheck, and the production build all pass; Node 20 stays supported), clearing the old Vitest-UI / Vite / tinypool advisories. docs/security.md records the re-reviewed post-upgrade advisories and why the remaining ones stay non-applicable or dev-only until the Next 15/16 chain lands.
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.
Closes the plan recorded in docs/security.md: move Vitest onto major 3 so the old Vitest-UI / Vite dev-server / tinypool advisories are retired, and re-review what npm audit reports after the move.
What changed
vitest2.1.9 -> 3.2.7 (exact pin, matching project policy; lockfile regenerated with the range normalized to exact).vitest.config.ts,vi.useFakeTimers(), and the node environment all behave identically.docs/security.md: advisory table rewritten against the post-upgrade audit output (theglobCLI finding actually comes viaeslint-config-next,@vitest/mockeris new-but-unused, and thenext/postcsschain is pinned until a Next major).CHANGELOG.md: entry under [Unreleased].Validation
npm test: 86/86 passed (5 files) on vitest 3.2.7npm run lint: cleannpm run typecheck: cleannpm run build: production build compiled, all routes presentnpm audit --audit-level=high: still non-zero — the gate stays advisory; the remaining majors require Next 15/16, and ESLint stays on 8 becauseeslint-config-next@14peers^7.23 || ^8.Notes
^18 || ^20 || >=22) keep CI's Node 20 supported.