Skip to content

chore(deps): update dependency @vitest/coverage-v8 to v3 #455

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

Open
wants to merge 1 commit into
base: main
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.2 age adoption passing confidence

Release Notes

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

v3.1.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v3.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.1.0

Compare Source

🚀 Features
🐞 Bug Fixes
🏎 Performance
View changes on GitHub

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 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 Updates to dependencies label Jan 16, 2025
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from bd340a4 to a94de27 Compare January 21, 2025 17:48
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from a94de27 to d02e239 Compare January 23, 2025 20:54
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from d02e239 to f1a06e4 Compare February 3, 2025 16:55
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v3 (major) chore(deps): update dependency @vitest/coverage-v8 to v3 Feb 4, 2025
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from a7b25ca to afba881 Compare February 24, 2025 20:04
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from afba881 to b57b747 Compare March 6, 2025 15:22
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from b57b747 to e928429 Compare March 17, 2025 18:42
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from e928429 to f4a7f30 Compare March 31, 2025 12:28
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from f4a7f30 to ecfa6af Compare April 21, 2025 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Updates to dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants