Skip to content

chore(deps): update dependency vitest to v4#43

Open
renovate[bot] wants to merge 1 commit into1.xfrom
renovate/major-vitest-monorepo
Open

chore(deps): update dependency vitest to v4#43
renovate[bot] wants to merge 1 commit into1.xfrom
renovate/major-vitest-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Nov 5, 2025 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vitest (source) ^3.2.3 → ^4.0.0 age confidence

Release Notes

vitest-dev/vitest (vitest)

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

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

renovate bot commented Nov 5, 2025 •
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 warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown project config "shamefully-hoist". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown project config "strict-peer-dependencies". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nuxt/test-utils@3.23.0
npm error Found: vitest@4.1.2
npm error node_modules/vitest
npm error   dev vitest@"^4.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional vitest@"^3.2.0" from @nuxt/test-utils@3.23.0
npm error node_modules/@nuxt/test-utils
npm error   dev @nuxt/test-utils@"^3.20.1" from the root project
npm error   @nuxt/test-utils@">=3.13.1" from vitest-environment-nuxt@1.0.1
npm error   node_modules/vitest-environment-nuxt
npm error     vitest-environment-nuxt@"^1.0.1" from @nuxt/test-utils@3.23.0
npm error
npm error Conflicting peer dependency: vitest@3.2.4
npm error node_modules/vitest
npm error   peerOptional vitest@"^3.2.0" from @nuxt/test-utils@3.23.0
npm error   node_modules/@nuxt/test-utils
npm error     dev @nuxt/test-utils@"^3.20.1" from the root project
npm error     @nuxt/test-utils@">=3.13.1" from vitest-environment-nuxt@1.0.1
npm error     node_modules/vitest-environment-nuxt
npm error       vitest-environment-nuxt@"^1.0.1" from @nuxt/test-utils@3.23.0
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-01T20_57_58_059Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-01T20_57_58_059Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 3d1e5cf to 7e20515 Compare November 5, 2025 09:09
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 7e20515 to 0f04055 Compare November 25, 2025 14:51
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 0f04055 to bf4318c Compare December 2, 2025 16:43
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from bf4318c to 1566711 Compare December 16, 2025 16:55
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 1566711 to 30c0f13 Compare January 19, 2026 15:56
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from b7d58e6 to d18d93b Compare February 19, 2026 07:58
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from d18d93b to b8512f9 Compare March 12, 2026 17:49
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from b8512f9 to 391023d Compare March 23, 2026 18:27
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 391023d to 61b95b0 Compare March 26, 2026 17:30
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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants