Skip to content

chore(deps): update vitest monorepo to v5 - #324

Open
ferrlabs-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo
Open

chore(deps): update vitest monorepo to v5#324
ferrlabs-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo

Conversation

@ferrlabs-renovate

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-v8 (source) ^4.1.8^5.0.0 age adoption passing confidence
vitest (source) ^4.1.8^5.0.0 age adoption passing confidence

Release Notes

vitest-dev/vitest (@​vitest/coverage-v8)

v5.0.0

Compare Source

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown

SonarQube — aucune nouvelle issue

Comparaison entre le projet bac à sable de cette PR et la branche par défaut : SonarQube Community n'analyse pas les PR, ce delta est calculé côté CI. Détail

@ferrfleet ferrfleet Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uneventful major bump for this repo.

What changed upstream (vitest/coverage-v8 4.1.11 → 5.0.0): biggest items are dropping Node 20 support (now requires Node ^22.12.0/^24/>=26), requiring Vite ^6.4, removing sequential test options in favor of concurrent, clearing mocks before each test by default, no longer walking up to ancestor directories for config discovery, and renaming toHaveTextContent to strict (new toMatchTextContent alias).

What breaks here: nothing found.

  • engines.node is already >=22.0.0 and CI is green, so the Node bump is a non-issue in practice (worth tightening to >=22.12.0 at some point for accuracy, but not blocking).
  • No use of .sequential(/sequential: anywhere in the repo.
  • Single vitest.config.ts at the repo root covers all packages (include: ['packages/**/__tests__/**/*.test.ts']) — no per-package configs that could be affected by the ancestor-lookup change.
  • Only mock-heavy test file (packages/mcp/src/tools/__tests__/docs.test.ts) creates a fresh vi.fn() per test rather than relying on cross-test mock state, so the "clear mocks by default" change doesn't affect it.
  • No custom istanbul reporter config, no imports from now-inlined internal packages (@vitest/expect, @vitest/runner, @vitest/spy).

CI: "Test / Test & Build" already passed on this head commit. Remaining checks (SonarQube, opengrep, zizmor) are still in progress but unrelated to this dependency.

@ferrlabs-renovate
ferrlabs-renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 00c196b to 1bad195 Compare September 5, 2026 17:37
@ferrlabs-renovate
ferrlabs-renovate Bot force-pushed the renovate/major-vitest-monorepo branch from 1bad195 to e09fa8c Compare September 5, 2026 22:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants