Skip to content

chore(deps): update dependency @vitest/coverage-v8 to v4#23

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

chore(deps): update dependency @vitest/coverage-v8 to v4#23
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Feb 5, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

Release Notes

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

v4.1.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.1.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.1.6

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.1.5

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.3

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.2

Compare Source

This release bumps Vitest's flatted version and removes version pinning to resolve flatted's CVE related issues (#​9975).

   🐞 Bug Fixes
    View changes on GitHub

v4.1.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.0

Compare Source

Vitest 4.1 is out!

This release page lists all changes made to the project during the 4.1 beta. To get a review of all the new features, read our blog post.

   🚀 Features
   🐞 Bug Fixes

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Only on Sunday and Saturday (* * * * 0,6)
  • Automerge
    • At any time (no schedule defined)

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

Rebasing: Whenever PR becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies label Feb 5, 2026
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 1d558fa to e19c95e Compare February 17, 2026 21:15
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch from e19c95e to 8e4f4c4 Compare March 5, 2026 16:05
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 6327474 to d3fe6ad Compare March 13, 2026 17:53
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from e200a3f to 17aecea Compare March 26, 2026 17:12
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 40dc054 to b652ec0 Compare April 9, 2026 11:08
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch from b652ec0 to 64d51dd Compare April 21, 2026 14:55
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch from 64d51dd to 60e6856 Compare April 29, 2026 10:55
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch from 60e6856 to a78e0a6 Compare May 11, 2026 15:51
@renovate renovate Bot changed the title chore(deps): update vitest monorepo to v4 (major) chore(deps): update vitest monorepo to v4 May 12, 2026
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 241a6f9 to 33b2e2e Compare May 20, 2026 10:56
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch from 33b2e2e to 9dae6a9 Compare May 28, 2026 17:11
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch from 9dae6a9 to fde7833 Compare June 1, 2026 22:08
@renovate renovate Bot changed the title chore(deps): update vitest monorepo to v4 chore(deps): update dependency @vitest/coverage-v8 to v4 Jun 1, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Jun 1, 2026

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @cap-js/console@1.0.2
npm error Found: vitest@3.2.6
npm error node_modules/vitest
npm error   dev vitest@"^3.2.4" from the root project
npm error   peer vitest@"3.2.6" from @vitest/ui@3.2.6
npm error   node_modules/@vitest/ui
npm error     peerOptional @vitest/ui@"3.2.6" from vitest@3.2.6
npm error
npm error Could not resolve dependency:
npm error peer vitest@"4.1.8" from @vitest/coverage-v8@4.1.8
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 this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-06-01T22_08_41_114Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-01T22_08_41_114Z-debug-0.log

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