Skip to content

chore(dev-deps): update vitest monorepo to v3 (major) - autoclosed #932

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 1, 2025

This PR contains the following updates:

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

Release Notes

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

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
    View changes on GitHub

v2.1.9

Compare Source

This release includes security patches for:

   🐞 Bug Fixes
    View changes on GitHub
vitest-dev/vitest (vitest)

v3.0.7

Compare Source

v3.0.6

Compare Source

   🐞 Bug Fixes

Configuration

📅 Schedule: Branch creation - "* 0-3 1 * *" (UTC), 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 renovate bot added 💙 Renovate Type: Maintenance Generic maintenance tasks, e.g., package updates. labels Feb 1, 2025
Copy link

graphite-app bot commented Feb 1, 2025

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • Status: Merge Queue - adds this PR to the back of the merge queue
  • Status: Hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 10 times, most recently from 33e688f to 6613638 Compare February 3, 2025 17:53
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 4 times, most recently from eed4fad to 31d45e9 Compare February 24, 2025 03:11
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 31d45e9 to 026827b Compare February 24, 2025 20:00
@renovate renovate bot changed the title chore(dev-deps): update vitest monorepo to v3 (major) chore(dev-deps): update vitest monorepo to v3 (major) - autoclosed Mar 8, 2025
@renovate renovate bot closed this Mar 8, 2025
@renovate renovate bot deleted the renovate/major-vitest-monorepo branch March 8, 2025 04:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💙 Renovate Type: Maintenance Generic maintenance tasks, e.g., package updates.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants