Skip to content

chore(deps): update dependency vitest to v5 - #172

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vitest-5.x
Open

chore(deps): update dependency vitest to v5#172
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vitest-5.x

Conversation

@renovate

@renovate renovate Bot commented Sep 14, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vitest (source) ^4.1.11 → ^5.0.0 age confidence

Release Notes

vitest-dev/vitest (vitest)

v5.0.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v5.0.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Europe/Berlin)

  • Branch creation
    • Between 08:00 AM and 05:59 PM, Monday through Friday (* 8-17 * * 1-5)
  • 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 commented Sep 14, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ 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: console/package-lock.json
npm warn Unknown env config "store". This will error in a future 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@4.1.0
npm error Found: vitest@5.0.1
npm error node_modules/vitest
npm error   dev vitest@"^5.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional vitest@"^4.0.2" from @nuxt/test-utils@4.1.0
npm error node_modules/@nuxt/test-utils
npm error   dev @nuxt/test-utils@"^4.1.0" from the root project
npm error   @nuxt/test-utils@"^4.0.0" from vitest-environment-nuxt@2.0.0
npm error   node_modules/vitest-environment-nuxt
npm error     vitest-environment-nuxt@"2.0.0" from @nuxt/test-utils@4.1.0
npm error
npm error Conflicting peer dependency: vitest@4.1.11
npm error node_modules/vitest
npm error   peerOptional vitest@"^4.0.2" from @nuxt/test-utils@4.1.0
npm error   node_modules/@nuxt/test-utils
npm error     dev @nuxt/test-utils@"^4.1.0" from the root project
npm error     @nuxt/test-utils@"^4.0.0" from vitest-environment-nuxt@2.0.0
npm error     node_modules/vitest-environment-nuxt
npm error       vitest-environment-nuxt@"2.0.0" from @nuxt/test-utils@4.1.0
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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-09-25T02_38_06_874Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-25T02_38_06_874Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/vitest-5.x branch from ebf057d to e0555e5 Compare September 22, 2026 23:23
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

breaking renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants