Skip to content

chore(deps): update vitest monorepo to v5.1.0 - #347

Merged
ferrlabs-renovate[bot] merged 1 commit into
mainfrom
renovate/vitest-monorepo
Nov 5, 2026
Merged

ferrlabs-renovate[bot] merged 1 commit into
mainfrom
renovate/vitest-monorepo

Conversation

@ferrlabs-renovate

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-v8 (source) 5.0.5 → 5.1.0 age adoption passing confidence
vitest (source) 5.0.5 → 5.1.0 age adoption passing confidence

Release Notes

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

v5.1.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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.

Signed-off-by: ferrlabs-renovate[bot] <282300760+ferrlabs-renovate[bot]@users.noreply.github.com>
@ferrlabs-renovate
ferrlabs-renovate Bot enabled auto-merge (squash) November 5, 2026 20:04

@ferrfleet-interne ferrfleet-interne 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.

Vitest and @vitest/coverage-v8 5.0.5 to 5.1.0, lockfile only. mcp/package.json keeps ^5.0.0, so the bump is within range.

What changed: the 5.1.0 release notes list only new features (--last-failed, --since-last-run, Temporal support in vi.setSystemTime, Node fake-timer support, browser-mode additions) and fixes. They list no breaking changes, removed APIs or changed defaults. The Node engine range is unchanged (^22.12 || ^24 || >=26), and the repo requires >=22.0.0.

What breaks here: nothing found. The repo only uses vitest run and vitest run --coverage (mcp/package.json scripts). It has no browser mode, and the browser-only changes, including the new default port, don't apply. The coverage-v8 changes are fixes or opt-in options. The transitive @vitest/istanbul-lib-* packages go from 1.0.2 to 2.1.0 and are internal to coverage-v8. They declare the same node >=22 engine.

CI: the Test, Lint, Quality and kind smoke jobs were still running when I reviewed. Nothing had failed. Check that they go green before merging.

@ferrlabs-renovate
ferrlabs-renovate Bot merged commit 8801a70 into main Nov 5, 2026
24 checks passed
@ferrlabs-renovate
ferrlabs-renovate Bot deleted the renovate/vitest-monorepo branch November 5, 2026 20:09
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