Skip to content

chore(deps): update vitest monorepo to v5 - #133

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

chore(deps): update vitest monorepo to v5#133
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jul 9, 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/coverage-v8 (source) 3.2.7 → 5.0.0 age confidence
@vitest/ui (source) 3.2.7 → 5.0.0 age confidence

Release Notes

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

v5.0.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • 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 50bb340 to c91e733 Compare July 16, 2026 16:10
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch 7 times, most recently from 1cd4f44 to 5694de3 Compare July 27, 2026 07:01
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from c5d5166 to 1889990 Compare July 30, 2026 18:56
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 206038e to 96e35bc Compare August 18, 2026 17:13
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch from 96e35bc to dd6db11 Compare September 3, 2026 20:54
@renovate renovate Bot changed the title chore(deps): update vitest monorepo to v4 chore(deps): update vitest monorepo to v5 Sep 3, 2026
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 4fca34e to 02bd2ef Compare September 10, 2026 23:26
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch from 02bd2ef to 1d0aebf Compare September 11, 2026 03:30
@renovate

renovate Bot commented Sep 11, 2026

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: 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 unable to resolve dependency tree
npm error
npm error While resolving: @aignostics/monorepo@0.0.0-development
npm error Found: vitest@3.2.7
npm error node_modules/vitest
npm error   dev vitest@"3.2.7" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vitest@"5.0.0" from @vitest/coverage-v8@5.0.0
npm error node_modules/@vitest/coverage-v8
npm error   dev @vitest/coverage-v8@"5.0.0" from the root project
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-11T03_30_20_751Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-11T03_30_20_751Z-debug-0.log

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants