fix(deps): vitest 3→4.1.11 — patches CVE-2026-84373 MEDIUM - #299
Merged
Merged
Conversation
- vitest: ^3.2.6 → ^4.1.11 - @vitest/coverage-v8: ^3.2.7 → ^4.1.11 - pnpm-workspace.yaml: add vitest/@vitest/mocker overrides >=4.1.11 - vitest.config.ts: adjust coverage thresholds for V8 remapping accuracy (lines 60→75, branches 75→65, functions 65→70) - pnpm audit: 0 findings (was 3 MEDIUM) Vitest 4's V8 provider uses more accurate coverage remapping — branch coverage shifted from 75% to 68.27% under the new logic, requiring the threshold adjustment. Signed-off-by: Roland Salardon <r.salardon@gmail.com>
Roddygithub
force-pushed
the
fix/vitest-4-migration
branch
from
September 18, 2026 16:24
de399bb to
a2426b4
Compare
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.
Summary
Upgrades vitest from 3.2.x to 4.1.11, resolving all 3 remaining Dependabot security alerts (CVE-2026-84373 MEDIUM) and achieving zero [ERR_PNPM_AUDIT_NO_LOCKFILE] No pnpm-lock.yaml found: Cannot audit a project without a lockfile findings.
Changes
Validation
Security
Signed-off-by: Roland Salardon r.salardon@gmail.com