Skip to content

build(deps-dev): upgrade vitest and @vitest/coverage-v8 to 5.0.5 - #161

Merged
cawalch merged 1 commit into
mainfrom
build/vitest-5
Nov 1, 2026
Merged

cawalch merged 1 commit into
mainfrom
build/vitest-5

Conversation

@cawalch

@cawalch cawalch commented Nov 1, 2026

Copy link
Copy Markdown
Collaborator

Upgrade the test runner to Vitest 5. @vitest/coverage-v8 pins the exact same Vitest version as its peer, so both move together — this supersedes #155 and #159, which cannot be merged safely one at a time (merging either alone leaves main with an unsatisfiable peer).

• Bump vitest and @vitest/coverage-v8 to ^5.0.5.
• No configuration changes were needed: vitest.config.mjs keeps the same test.coverage shape, v8 provider, reporters, and thresholds.
• Vitest 5 requires Node.js ^22.12.0 || ^24.0.0 || >=26.0.0, which the matrix now covers after #160. Node 20 and 23 are no longer usable for development, matching their EOL status.

Verification

On Node.js 26.13.0:

  • npm test — 1,380 tests passed across 13 files.
  • npm run coverage — thresholds pass: statements 95.66% (≥95), branches 91.93% (≥90), functions 95.83% (≥95), lines 95.54% (≥95); coverage/lcov.info still produced for the workflow artifact.
  • npm run lint:ci and npm run build — passed.
  • Coverage moved slightly (statements 95.70% → 95.66%, lines 95.58% → 95.54%) because Vitest 5's v8 provider reports a few more lines; well above the configured floors.

Move the test runner to v5; the coverage provider is peer-locked to the exact same version, so both move together.

• Bump `vitest` and `@vitest/coverage-v8` to `^5.0.5`.
• No configuration changes were needed: `vitest.config.mjs` keeps the same `test.coverage` shape, reporters, and thresholds.
@cawalch
cawalch merged commit 678cff6 into main Nov 1, 2026
9 checks passed
@cawalch
cawalch deleted the build/vitest-5 branch November 1, 2026 16:31
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