Skip to content

Update vitest monorepo to v4#98

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

Update vitest monorepo to v4#98
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo

Conversation

@renovate

@renovate renovate Bot commented Apr 10, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@vitest/coverage-v8 (source) 1.6.14.1.8 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: (in timezone America/Los_Angeles)

  • Branch creation
    • Monday through Friday (* * * * 1-5)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch 10 times, most recently from a8b0768 to d6cabad Compare April 17, 2026 01:56
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch 5 times, most recently from b2fe9f4 to b430810 Compare April 24, 2026 15:30
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch 4 times, most recently from 1da681a to da3ce49 Compare April 30, 2026 20:35
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 41c7b70 to e6a8059 Compare May 11, 2026 18:10
@renovate renovate Bot changed the title Update vitest monorepo to v4 (major) Update vitest monorepo to v4 May 12, 2026
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch 4 times, most recently from 4b534e7 to 3dd637d Compare May 18, 2026 07:05
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 21cfcff to e1d20eb Compare May 28, 2026 18:12
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch from e1d20eb to 48ba620 Compare June 1, 2026 20:49
@renovate renovate Bot changed the title Update vitest monorepo to v4 Update dependency @vitest/coverage-v8 to v4 Jun 1, 2026
@renovate renovate Bot changed the title Update dependency @vitest/coverage-v8 to v4 Update vitest monorepo to v4 Jun 2, 2026
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from f8fcb75 to c26f288 Compare June 8, 2026 16:13
@renovate renovate Bot force-pushed the renovate/major-vitest-monorepo branch from c26f288 to 0a4f40e Compare June 8, 2026 22:15
@renovate

renovate Bot commented Jun 8, 2026

Copy link
Copy Markdown
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: convex-test@0.0.53
npm error Found: vitest@1.6.1
npm error node_modules/vitest
npm error   dev vitest@"1.6.1" from the root project
npm error   peer vitest@"1.6.1" from @vitest/ui@1.6.1
npm error   node_modules/@vitest/ui
npm error     peerOptional @vitest/ui@"1.6.1" from vitest@1.6.1
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.1.8" 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 /runner/cache/others/npm/_logs/2026-06-11T11_54_01_185Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-11T11_54_01_185Z-debug-0.log

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.

0 participants