Skip to content

Conversation

@balena-renovate
Copy link
Contributor

@balena-renovate balena-renovate bot commented Oct 25, 2025

This PR contains the following updates:

Package Change Age Confidence
@vitest/coverage-v8 (source) ^3.0.0 -> ^4.0.0 age confidence

Release Notes

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

v4.0.15

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.0.14

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.0.13

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.0.12

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.11

Compare Source

   🚀 Experimental Features
   🏎 Performance
    View changes on GitHub

v4.0.10

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.9

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.0.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.7

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.0.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.5

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.0.4

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.0.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.0

Compare Source

Vitest 4.0 is out!

To stay updated, read our blog post and check the migration guide.

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes

Configuration

📅 Schedule: 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR has been generated by Renovate Bot.

Update @vitest/coverage-v8 from 3.2.4 to 4.0.0

Change-type: patch
@balena-renovate
Copy link
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/vitest
npm error   dev vitest@"^3.0.0" from the root project
npm error   peer vitest@"3.2.4" from @vitest/[email protected]
npm error   node_modules/@vitest/ui
npm error     peerOptional @vitest/ui@"3.2.4" from [email protected]
npm error
npm error Could not resolve dependency:
npm error peer vitest@"4.0.3" from @vitest/[email protected]
npm error node_modules/@vitest/coverage-v8
npm error   dev @vitest/coverage-v8@"^4.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-10-25T15_06_14_166Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-10-25T15_06_14_166Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant