fix(deps): update dependency vitest to v2 #1987
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Warning Rate limit exceeded@renovate[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 7 minutes and 22 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. WalkthroughWalkthroughThe recent updates to the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
|
Here's the code health analysis summary for commits Analysis Summary
|
![codecov[bot]](https://avatars.githubusercontent.com/in/254?s=60&v=4){kind=small}
There was a problem hiding this comment.
The code changes mostly revolve around updating the version of the 'vitest' package from 1.6.0 to 2.0.0 across multiple dependent packages. Generally speaking, this seems to be a straightforward upgrade. However, it's necessary to ensure compatibility of the 'vitest' version 2.0.0 with all packages. Additionally, if any breaking changes or additional features are introduced in version 2.0.0 of 'vitest', necessary changes should be implemented across all packages which utilize it. In addition, testing should be done to ensure no functionality is broken as a result of this version upgrade.
There was a problem hiding this comment.
This review concerns several updates to the project's package dependencies. Specifically, 'vitest' has been updated from version '1.6.0' to '2.0.0' across multiple packages. There is also an update to '@vitest/coverage-v8' from version '1.6.0' to '2.0.0'. While code changes are not present, it is essential to confirm that the packages behave as expected after the upgrade, particularly taking into account possible breaking changes between major versions.
There was a problem hiding this comment.
The Git diff reveals that the version update from version '1.6.0' to '2.0.0' for the package 'vitest' across different microservices. This is a major change and there should be comprehensive testing done to ensure nothing breaks after the update since major versions typically introduce breaking changes.
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## dev #1987 +/- ##
=======================================
Coverage 33.20% 33.20%
=======================================
Files 207 207
Lines 13593 13593
Branches 409 460 +51
=======================================
Hits 4513 4513
Misses 9080 9080
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
44a6a41
to
d6b8703
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
d6b8703
to
1fd713f
Compare
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
|
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
1fd713f
to
d32dace
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
d32dace
to
7d7ad36
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
7d7ad36
to
9bab8c1
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
9bab8c1
to
7d20c42
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
7d20c42
to
7742adb
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
Files selected for processing (1)
- package.json (2 hunks)
Files skipped from review due to trivial changes (1)
- package.json
Head branch was modified
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
7742adb
to
deff213
Compare
renovate
bot
dismissed
coderabbitai’s stale review
The base branch was changed.
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
Files selected for processing (1)
- package.json (2 hunks)
Files skipped from review as they are similar to previous changes (1)
- package.json
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
deff213
to
f5facbb
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
f5facbb
to
1a7f842
Compare
renovate
bot
force-pushed
the
renovate/major-vitest-monorepo
branch
from
1a7f842
to
44eeff4
Compare
|
github-merge-queue
bot
removed this pull request from the merge queue due to Branch Protection failures
This PR contains the following updates:
^1.6.0->^2.0.5Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
vitest-dev/vitest (vitest)
v2.0.5Compare Source
🚀 Features
🐞 Bug Fixes
testNamePatternadds leading space - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6186 (073a5)afterEachcleanup hooks in node entrypoint - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6192 (e6fbc)defineProjectanddefineWorkspacetypes - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6198 (8cd82)node:*imports in__mocks__folder - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6204 (a48be)View changes on GitHub
v2.0.4Compare Source
🐞 Bug Fixes
require- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6159 (807a2)*.ctsfiles - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6189 (5da45)thresholds.<glob>.100option - by @thor-juhasz and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6174 (f6845)mockImplementationfor function overload and unions - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6181 (7a75b)View changes on GitHub
v2.0.3Compare Source
🚀 Features
🐞 Bug Fixes
--inspect-brkstop on Windows - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6110 (f8519)vi.spyOntoMockInstanceof function overload - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6086 (e9f9a)View changes on GitHub
v2.0.2Compare Source
v2.0.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.0.0Compare Source
Vitest 2.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
--segfault-retry- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5514 (ed60e)threadssegfaults. Our current recommendation is to use the new defaultforkspool instead.onTestFinishedhook. This can make your tests run a little bit slower.coverage.ignoreEmptyLinesby default - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5543 (31994)locationfield pointed to the error location instead of the test location. Now it is aligned with jest and contains thelineandcolumnof a test function, but requiresincludeTaskLocationto be enabled.poolto'forks'- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5047 (7f8f9)threadspool: https://vitest.dev/guide/improving-performance.html#pool--merge-reportsto support coverage - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5736 (b7438)spy.mock.returns. If the function is async or returns a promise, it will always succeed and have aPromiseinresults. To make migration easier, we introducedspy.mock.settledResultsthat unwraps promises andexpect().toHaveResolved()matcher that accepts unwrapped value.jsonoutput - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5802 (dd754)indexScriptstoorchestratorScriptsin the browser config - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5842 (49f34)poolAPI - now requirescollectTestsmethod alongsiderunTests.🚀 Features
--output-json- by @Joristdh in https://github.com/vitest-dev/vitest/issues/5745 (0766b)parseAst,parseAstAsyncfrom vite - by @sheremet-va (f645e)clickevent - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5777 (839c3)page.screenshotmethod - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5853 (81c42)userEventmethods, addfillanddragAndDropevents - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5882 (4dbea)expect.dommethod and bundlejest-dommatchers with@vitest/browser- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5910 (3a96a)tripleClickto interactive api - by @userquin in https://github.com/vitest-dev/vitest/issues/5987 (200a4)test.for- by @hi-ogawa and @sheremet-va in https://github.com/vitest-dev/vitest/issues/5861 (c2380)🐞 Bug Fixes
--excludeoption - by @fregante in https://github.com/vitest-dev/vitest/issues/5782 (d6700)project.providetype - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5959 (0eda9)previewprovider when running in StackBlitz - by @userquin in https://github.com/vitest-dev/vitest/issues/5836 (76e13)coverage.reporterfrom string values - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5920 (f33da)thresholds.autoUpdateto supportmergeConfig- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5818 (7afb3)stderrofstartVitest()- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5954 (70805)exclude- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5997 (169bc)else- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6014 (368c1)test-excludeto v7 - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5867 (0a715)poolOptions.<name>.isolatefromforksoptions - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5840 (a60a1)toMatchFileSnapshotwith empty file - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5894 (88006)FileDetailstitle status icon not being updated - by @userquin in https://github.com/vitest-dev/vitest/issues/5942 (e9ddf)VITE_- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6017 (d87be)provideto the public API - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5897 (66e64)View changes on GitHub
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.