-
Notifications
You must be signed in to change notification settings - Fork 16
chore(deps): update vitest monorepo to v2.1.1 #2095
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
Conversation
Branch automerge failureThis PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This commit correctly updates the versions of @vitest/coverage-v8 in both the package.json files and the pnpm-lock.yaml. One thing I noticed in the pnpm-lock.yaml is the removal of [email protected] from the [email protected] snapshots and also entirely from the optionalDependencies. This could completely remove the pg package from this project. Make sure that the pg package is not in use anywhere else in the project or this could potentially break things.
| '@adminjs/sequelize': | ||
| specifier: ^4.1.1 | ||
| version: 4.1.1([email protected](@types/[email protected]))([email protected]([email protected])) | ||
| version: 4.1.1([email protected](@types/[email protected]))([email protected]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here the version of pg is removed as a direct dependency of @adminjs/sequelize. If pg is used elsewhere in the project, make sure it's being required properly.
| specifier: link:packages/transactions | ||
| version: link:packages/transactions | ||
| sequelize: | ||
| specifier: ^6.35.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pg is removed as a version specifier for sequelize here. Check to ensure this doesn't unintentionally affect areas of your codebase.
| sequelize: 6.37.3([email protected]) | ||
| sequelize: 6.37.3 | ||
|
|
||
| '@ampproject/[email protected]': |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pg is removed from the optionalDependencies completely here. If pg is an optional dependency elsewhere in the project, you might want to add it back.
| - prop-types | ||
| - react-is | ||
| - supports-color | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Be aware that removing pg as a dependency of sequelize here could affect your data layer if sequelize is interacting with a postgres database.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The updates in the Git diff primarily consist of package version updates in multiple package.json files and the pnpm-lock.yaml file. The change from version '2' to '2.0.5' might affect the functionality of the '@vitest/coverage-v8' dependent features if the new version introduces breaking changes or removes features the project relies on. Additionally, the sequelize package in pnpm-lock.yaml has been updated to remove the 'pg' sub-dependency, this could impact the database interfacing that relies on postgres. Explicit versioning is a good practice for maintaining consistency across environments but these changes need to be tested properly.
packages/database/package.json
Outdated
| "description": "", | ||
| "devDependencies": { | ||
| "@vitest/coverage-v8": "2", | ||
| "@vitest/coverage-v8": "2.0.5", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The version of '@vitest/coverage-v8' is updated across the packages. Check if there are breaking changes in version '2.0.5' that the project might not support.
| '@adminjs/sequelize': | ||
| specifier: ^4.1.1 | ||
| version: 4.1.1([email protected](@types/[email protected]))([email protected]([email protected])) | ||
| version: 4.1.1([email protected](@types/[email protected]))([email protected]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The explicit Postgres dependency denoted as 'pg' has been removed from sequelize package version. Confirm that 'sequelize' package functionality compatible with the Postgres database isn't affected by this change.
| specifier: link:packages/transactions | ||
| version: link:packages/transactions | ||
| sequelize: | ||
| specifier: ^6.35.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The explicit 'pg' sub-dependency has been removed from 'sequelize'. It is required to verify this change is not affecting the project's database interactions that rely on Postgres.
| sequelize: 6.37.3([email protected]) | ||
| sequelize: 6.37.3 | ||
|
|
||
| '@ampproject/[email protected]': |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The optional 'pg' dependency for the 'sequelize' package has been removed. Ensure that this change does not affect the project's Postgres-based functionalities.
|
Here's the code health analysis summary for commits Analysis Summary
|
b967710 to
2e00a69
Compare
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 #2095 +/- ##
=======================================
Coverage 29.58% 29.58%
=======================================
Files 222 222
Lines 12545 12545
Branches 526 475 -51
=======================================
Hits 3712 3712
Misses 8833 8833
☔ View full report in Codecov by Sentry. |
4712886 to
5763334
Compare
5763334 to
eb87c43
Compare
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected] |
eb87c43 to
60697e0
Compare
60697e0 to
d5e4ba1
Compare
230d2b7 to
8773659
Compare
8773659 to
c671836
Compare
|



This PR contains the following updates:
2->2.1.12.0.5->2.1.1^2.0.5->^2.1.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
vitest-dev/vitest (@vitest/coverage-v8)
v2.1.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.1.0Compare Source
This release makes another big change to the Browser Mode by introducing locators API:
You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the
pageobject from@vitest/browser/context.🚀 Features
userEvent.uploadin playwright provider - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6442 (cf148)--inspect- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6433 (0499a)--inspect-brk- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6434 (7ab0f)--exclude-after-remap- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6309 (5932a){ spy: true }instead of a factory - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6289 (95f02)vi.advanceTimersToNextFrame- by @bnjm and @sheremet-va in https://github.com/vitest-dev/vitest/issues/6347 (8ff63)🐞 Bug Fixes
indexfile - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6266 (081cf)expect.getState().testPathalways returns correct path - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6472 (ac698)vitestand@vitest/*versions don't match - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6317 (e662c)vitenodefor uncovered files - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6044 (da52d)performance.nowinstead ofDate.nowfor duration - by @LuciNyan in https://github.com/vitest-dev/vitest/issues/6382 (fe489)toMatchInlineSnapshotupdates at the same location - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6332 (1606f)typecheck.includeoverlaps withinclude- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6256 (153ff)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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.