Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 16, 2025

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Change Age Confidence
@vitest/coverage-v8 (source) 2.1.8 -> 3.2.4 age confidence
@vitest/ui (source) 2.1.8 -> 3.2.4 age confidence

Release Notes

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

v3.2.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.2.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.2.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.2.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.2.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.1.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.1.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.1.2

Compare Source

   🐞 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

   🐞 Bug Fixes
    View changes on GitHub

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

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.

@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 4 times, most recently from f06e15a to ec1be9e Compare January 23, 2025 13:53
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from ec1be9e to 311324b Compare February 3, 2025 16:29
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 311324b to 7ef92c4 Compare February 18, 2025 19:21
@renovate
Copy link
Contributor Author

renovate bot commented Feb 18, 2025

⚠️ 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.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: rxjs-collection@0.0.0
npm error Found: vitest@2.1.8
npm error node_modules/vitest
npm error   dev vitest@"2.1.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vitest@"3.2.4" from @vitest/coverage-v8@3.2.4
npm error node_modules/@vitest/coverage-v8
npm error   dev @vitest/coverage-v8@"3.2.4" from the root project
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/2025-08-31T10_02_45_082Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-08-31T10_02_45_082Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 7ef92c4 to 963e7ac Compare February 24, 2025 18:48
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 963e7ac to 91be553 Compare March 6, 2025 19:39
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 91be553 to 5db6f12 Compare March 17, 2025 17:44
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 5db6f12 to ad11a89 Compare March 31, 2025 11:51
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from ad11a89 to 0c27710 Compare April 21, 2025 10:31
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 0c27710 to e08bd4a Compare May 5, 2025 15:46
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from e08bd4a to ad1d5eb Compare May 19, 2025 20:55
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 473399d to c64bc95 Compare June 5, 2025 14:05
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from c64bc95 to 1e95c20 Compare June 9, 2025 13:09
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 1e95c20 to b6dbcb2 Compare June 17, 2025 19:31
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v3 (major) chore(deps): update vitest monorepo to v3 (major) - abandoned Sep 17, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Sep 17, 2025

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

@ThornWalli ThornWalli closed this Sep 17, 2025
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.

2 participants