Skip to content

chore(deps): update vitest monorepo to v4 (major)#38

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

chore(deps): update vitest monorepo to v4 (major)#38
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-vitest-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Nov 3, 2025

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

Release Notes

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

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

v4.0.18

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.0.17

Compare Source

   🚀 Experimental 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.

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 3bc4427 to c4608c3 Compare November 7, 2025 16:37
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 03fbbe3 to 9ed0a43 Compare November 20, 2025 12:32
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from e7bce88 to 3c5733c Compare November 25, 2025 14:00
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 3c5733c to 6fa72d7 Compare December 2, 2025 18:06
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 6fa72d7 to ee0aeaf Compare December 16, 2025 18:51
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from ee0aeaf to 79a8cf0 Compare December 31, 2025 15:14
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from ff8e2da to e6c881d Compare January 16, 2026 13:24
@renovate renovate bot changed the title chore(deps): update dependency vitest to v4 chore(deps): update vitest monorepo to v4 (major) Jan 16, 2026
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 079d467 to 49b370c Compare January 22, 2026 20:28
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 49b370c to c156940 Compare February 3, 2026 07:09
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from c156940 to 03dc366 Compare February 12, 2026 13:36
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 4 times, most recently from cb9b6a0 to 2d4fdf9 Compare March 5, 2026 20:14
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 2d4fdf9 to 7a4310d Compare March 12, 2026 14:42
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 7a4310d to b5800f5 Compare March 31, 2026 18:44
@sonarqubecloud
Copy link
Copy Markdown

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