Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency vitest to v1 - autoclosed #346

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 7, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) 0.31.4 -> 1.1.3 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

v1.1.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.1.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.1.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.0.4

Compare Source

The previous release was built incorrectly and didn't include the performance fix. This release fixes that.

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v1.0.3

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v1.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.0.0

Compare Source

Vitest 1.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.34.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.34.5

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 has been generated by Mend Renovate. View repository job log here.

Copy link
Contributor Author

renovate bot commented Dec 7, 2023

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @vitest/coverage-c8@0.31.4
npm ERR! Found: vitest@1.1.3
npm ERR! node_modules/vitest
npm ERR!   dev vitest@"1.1.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vitest@">=0.30.0 <1" from @vitest/coverage-c8@0.31.4
npm ERR! node_modules/@vitest/coverage-c8
npm ERR!   dev @vitest/coverage-c8@"0.31.4" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: vitest@0.34.6
npm ERR! node_modules/vitest
npm ERR!   peer vitest@">=0.30.0 <1" from @vitest/coverage-c8@0.31.4
npm ERR!   node_modules/@vitest/coverage-c8
npm ERR!     dev @vitest/coverage-c8@"0.31.4" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-01-12T18_09_45_396Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-01-12T18_09_45_396Z-debug-0.log

Copy link

github-actions bot commented Dec 7, 2023

Test Results

 1 files  ±0   4 suites  ±0   0s ⏱️ ±0s
60 tests ±0  60 ✅ ±0  0 💤 ±0  0 ❌ ±0 
64 runs  ±0  64 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit f8657d4. ± Comparison against base commit fc89def.

♻️ This comment has been updated with latest results.

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 8 times, most recently from 96b5703 to a0b0736 Compare December 12, 2023 19:58
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 6 times, most recently from 16bb21a to bfc8583 Compare December 21, 2023 19:09
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 4 times, most recently from 23cb5d4 to 651561b Compare December 28, 2023 19:00
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 5 times, most recently from 1e4e2cb to 77da905 Compare January 5, 2024 01:21
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 4 times, most recently from 7ba2f04 to f8657d4 Compare January 11, 2024 01:06
Copy link

Code Coverage

Package Line Rate Branch Rate Complexity Health
src 100% 100% 0
src.lib 100% 100% 0
Summary 100% (429 / 429) 100% (87 / 87) 0

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from f8657d4 to bb5827a Compare January 12, 2024 03:10
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from bb5827a to 6d79dab Compare January 12, 2024 18:09
@renovate renovate bot changed the title chore(deps): update dependency vitest to v1 chore(deps): update dependency vitest to v1 - autoclosed Jan 12, 2024
@renovate renovate bot closed this Jan 12, 2024
@renovate renovate bot deleted the renovate/major-vitest-monorepo branch January 12, 2024 23:13
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.

None yet

0 participants