Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update vitest monorepo to v3 (major) #119

Open
wants to merge 1 commit into
base: beta
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 16, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-v8 (source) 2.1.8 -> 3.1.1 age adoption passing confidence
@vitest/ui (source) 2.1.8 -> 3.1.1 age adoption passing confidence

Release Notes

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

v3.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.1.0

Compare Source

v3.0.9

Compare Source

v3.0.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.7

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v3.0.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.5

Compare Source

This release includes security patches for:

🚀 Features
🐞 Bug Fixes
View changes on GitHub

v3.0.4

Compare Source

This release includes security patches for:

   🐞 Bug Fixes
    View changes on GitHub

v3.0.3

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v3.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.0

Compare Source

Vitest 3 is here! There are a few breaking changes, but we expect the migration to be smooth. This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.

   🚨 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 becomes conflicted, 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.

Copy link

stackblitz bot commented Jan 16, 2025

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 4 times, most recently from f06e15a to ec1be9e Compare January 23, 2025 13:53
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from ec1be9e to 311324b Compare February 3, 2025 16:29
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 311324b to 7ef92c4 Compare February 18, 2025 19:21
Copy link
Contributor Author

renovate bot commented Feb 18, 2025

⚠️ 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.
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@"2.1.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vitest@"3.1.1" from @vitest/[email protected]
npm error node_modules/@vitest/coverage-v8
npm error   dev @vitest/coverage-v8@"3.1.1" 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/2025-03-31T11_51_41_546Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-03-31T11_51_41_546Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 7ef92c4 to 963e7ac Compare February 24, 2025 18:48
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 963e7ac to 91be553 Compare March 6, 2025 19:39
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 91be553 to 5db6f12 Compare March 17, 2025 17:44
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 5db6f12 to ad11a89 Compare March 31, 2025 11:51
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