Skip to content

Update vitest monorepo to v4 (major)#32

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

Update vitest monorepo to v4 (major)#32
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-vitest-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Apr 7, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

Release Notes

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

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
   🏎 Performance

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 these updates 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
Copy link
Copy Markdown
Contributor Author

renovate bot commented Apr 7, 2026 •
edited
Loading

⚠️ 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 could not resolve
npm error
npm error While resolving: @fast-check/vitest@0.1.6
npm error Found: vitest@4.1.4
npm error node_modules/vitest
npm error   dev vitest@"^4.0.0" from the root project
npm error   peer vitest@"4.1.4" from @vitest/coverage-v8@4.1.4
npm error   node_modules/@vitest/coverage-v8
npm error     dev @vitest/coverage-v8@"^4.0.0" from the root project
npm error     peerOptional @vitest/coverage-v8@"4.1.4" from vitest@4.1.4
npm error
npm error Could not resolve dependency:
npm error peer vitest@">=0.28.1 <1.0.0 || ^1 || ^2 || ^3" from @fast-check/vitest@0.1.6
npm error node_modules/@fast-check/vitest
npm error   dev @fast-check/vitest@"^0.1.3" from the root project
npm error
npm error Conflicting peer dependency: vitest@3.2.4
npm error node_modules/vitest
npm error   peer vitest@">=0.28.1 <1.0.0 || ^1 || ^2 || ^3" from @fast-check/vitest@0.1.6
npm error   node_modules/@fast-check/vitest
npm error     dev @fast-check/vitest@"^0.1.3" 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-04-15T05_27_02_512Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-15T05_27_02_512Z-debug-0.log

@renovate renovate bot changed the title chore(deps): update vitest monorepo to v4 (major) Update vitest monorepo to v4 (major) Apr 8, 2026
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from b84ead5 to ecf9d5b Compare April 15, 2026 05:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants