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 vitest monorepo to v1.5.0 #1884

Merged
merged 1 commit into from
Apr 11, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 11, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-v8 (source) 1.4.0 -> 1.5.0 age adoption passing confidence
vitest (source) 1.4.0 -> 1.5.0 age adoption passing confidence

Release Notes

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

v1.5.0

Compare Source

vitest-dev/vitest (vitest)

v1.5.0

Compare Source


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 these updates 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.

@renovate renovate bot enabled auto-merge (squash) April 11, 2024 19:07
Copy link

coderabbitai bot commented Apr 11, 2024

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.


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?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

deepsource-io bot commented Apr 11, 2024

Here's the code health analysis summary for commits e7fe037..70bb915. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource JavaScript LogoJavaScript✅ SuccessView Check ↗

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

Copy link

sonarcloud bot commented Apr 11, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

Copy link

Removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: npm/@vitest/coverage-v8@1.4.0, npm/vitest@1.4.0

View full report↗︎

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the given code diff, various libraries and their dependencies have been updated to newer versions. We have upgraded libraries like @vitest/coverage-v8, vitest and all dependencies locked with '@vitest'. It is important to check the new libraries for any breaking changes which could affect the code. Further, unit and integration tests should be run to confirm that the changes have not inadvertently affected the app functionality. Also, if these libraries were upgraded to fix specific issues, we should verify that those have been resolved.

@@ -28,15 +28,15 @@
"@sentry/profiling-node": "7.110.0",
"@slonik/migrator": "0.12.0",
"@types/node": "20.12.7",
"@vitest/coverage-v8": "1.4.0",
"@vitest/coverage-v8": "1.5.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vitest/coverage-v8 library has been upgraded from version 1.4.0 to 1.5.0. Validate that this update does not introduce offences and the reason for the update was necessary. Also check the newer version for any deprecated features/known issues.

"esbuild": "0.20.2",
"eslint": "8.57.0",
"eslint-config-prettier": "9.1.0",
"eslint-plugin-prettier": "5.1.3",
"npm-run-all2": "6.1.2",
"prettier": "3.2.5",
"typescript": "5.4.5",
"vitest": "1.4.0"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The version of the vitest library has been lifted from 1.4.0 to 1.5.0. Run the existing unit test suite to make sure this update does not break anything. Also, ensure that this version does not have deprecated features that might be used in the application.

specifier: 1.4.0
version: 1.4.0(vitest@1.4.0)
specifier: 1.5.0
version: 1.5.0(vitest@1.5.0)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In pnpm-lock.yaml, '@vitest/coverage-v8' version has also been updated to 1.5.0, justifying a similar check for incompatibility or breaking changes as suggested above.

@@ -82,8 +82,8 @@ importers:
specifier: 5.4.5
version: 5.4.5
vitest:
specifier: 1.4.0
version: 1.4.0(@types/node@20.12.7)
specifier: 1.5.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'vitest' version update to 1.5.0 in pnpm-lock.yaml should not have any conflicts with other packages, any deprecated features, or any other known issues.

/@vitest/coverage-v8@1.4.0(vitest@1.4.0):
resolution: {integrity: sha512-4hDGyH1SvKpgZnIByr9LhGgCEuF9DKM34IBLCC/fVfy24Z3+PZ+Ii9hsVBsHvY1umM1aGPEjceRkzxCfcQ10wg==}
/@vitest/coverage-v8@1.5.0(vitest@1.5.0):
resolution: {integrity: sha512-1igVwlcqw1QUMdfcMlzzY4coikSIBN944pkueGi0pawrX5I5Z+9hxdTR+w3Sg6Q3eZhvdMAs8ZaF9JuTG1uYOQ==}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'vitest' has been updated as a peerDependency, requiring the version to be 1.5.0.

@@ -1333,44 +1329,43 @@ packages:
std-env: 3.7.0
strip-literal: 2.1.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The version for 'vitest' under package '@vitest/coverage-v8' has been updated to 1.5.0 in pnpm-lock.yaml. Look over the corresponding changes and address any issues.

/@vitest/expect@1.4.0:
resolution: {integrity: sha512-Jths0sWCJZ8BxjKe+p+eKsoqev1/T8lYcrjavEaz8auEJ4jAVY0GwW3JKmdVU4mmNPLPHixh4GNXP7GFtAiDHA==}
/@vitest/expect@1.5.0:
resolution: {integrity: sha512-0pzuCI6KYi2SIC3LQezmxujU9RK/vwC1U9R0rLuGlNGcOuDWxqWKu6nUdFsX9tH1WU0SXtAxToOsEjeUn1s3hA==}
dependencies:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'@vitest/spy' has been updated from version 1.4.0 to 1.5.0. Check for any incompatibility or breaking changes.

chai: 4.4.1
dev: true

/@vitest/runner@1.4.0:
resolution: {integrity: sha512-EDYVSmesqlQ4RD2VvWo3hQgTJ7ZrFQ2VSJdfiJiArkCerDAGeyF1i6dHkmySqk573jLp6d/cfqCN+7wUB5tLgg==}
/@vitest/runner@1.5.0:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'@vitest/utils' has been updated from version 1.4.0 to 1.5.0. Validate it for any incompatibility or breaking changes due to the version upgrade.

/@vitest/spy@1.4.0:
resolution: {integrity: sha512-Ywau/Qs1DzM/8Uc+yA77CwSegizMlcgTJuYGAi0jujOteJOUf1ujunHThYo243KG9nAyWT3L9ifPYZ5+As/+6Q==}
/@vitest/spy@1.5.0:
resolution: {integrity: sha512-vu6vi6ew5N5MMHJjD5PoakMRKYdmIrNJmyfkhRpQt5d9Ewhw9nZ5Aqynbi3N61bvk9UvZ5UysMT6ayIrZ8GA9w==}
dependencies:
tinyspy: 2.2.1
dev: true
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Notice the update in package '@vitest/utils' to version 1.5.0 in pnpm-lock.yaml. Make sure this change is reviewed thoroughly and tested extensively.

/vite-node@1.4.0(@types/node@20.12.7):
resolution: {integrity: sha512-VZDAseqjrHgNd4Kh8icYHWzTKSCZMhia7GyHfhtzLW33fZlG9SwsB6CEhgyVOWkJfJ2pFLrp/Gj1FSfAiqH9Lw==}
/vite-node@1.5.0(@types/node@20.12.7):
resolution: {integrity: sha512-tV8h6gMj6vPzVCa7l+VGq9lwoJjW8Y79vst8QZZGiuRAfijU+EEWuc0kFpmndQrWhMMhet1jdSF+40KSZUqIIw==}
engines: {node: ^18.0.0 || >=20.0.0}
hasBin: true
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'vitest' package upgraded to version 1.5.0, run the existing unit test suite to make sure this update does not break anything.

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes in this diff primarily involve package updates from version 1.4.0 to 1.5.0. This includes updates to @vitest/coverage-v8, vitest, and their dependencies. It appears that these updates are well synchronized across package.json and pnpm-lock.yaml. One package, @types/istanbul-lib-coverage@2.0.6, and its dependent, v8-to-istanbul, have been removed. It is important to ensure that the removal of this package does not negatively affect the functionality of other components.

@@ -28,15 +28,15 @@
"@sentry/profiling-node": "7.110.0",
"@slonik/migrator": "0.12.0",
"@types/node": "20.12.7",
"@vitest/coverage-v8": "1.4.0",
"@vitest/coverage-v8": "1.5.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The @vitest/coverage-v8 package has been updated from version 1.4.0 to 1.5.0. Please ensure that this new version maintains compatibility with the project and that all features dependant on this package work as expected.

@@ -28,15 +28,15 @@
"@sentry/profiling-node": "7.110.0",
"@slonik/migrator": "0.12.0",
"@types/node": "20.12.7",
"@vitest/coverage-v8": "1.4.0",
"@vitest/coverage-v8": "1.5.0",
"esbuild": "0.20.2",
"eslint": "8.57.0",
"eslint-config-prettier": "9.1.0",
"eslint-plugin-prettier": "5.1.3",
"npm-run-all2": "6.1.2",
"prettier": "3.2.5",
"typescript": "5.4.5",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The vitest package was updated from version 1.4.0 to 1.5.0. Make sure to test the areas of your application that utilizes this package to ensure continued functionality.

@@ -1295,10 +1295,6 @@ packages:
resolution: {integrity: sha512-/kYRxGDLWzHOB7q+wtSUQlFrtcdUccpfy+X+9iMBpHK8QLLhx2wIPYuS5DYtR9Wa/YlZAbIovy7qVdB1Aq6Lyw==}
dev: true

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The @types/istanbul-lib-coverage@2.0.6 package has been removed. Please confirm whether any elements in the codebase needing those types have been updated or are otherwise unaffected by this removal.

@@ -3651,15 +3647,6 @@ packages:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'v8-to-istanbul', which depends on the removed @types/istanbul-lib-coverage, was also removed. Check for any dependencies in the code that might be affected by the removal of this package.

@@ -1315,10 +1311,10 @@ packages:
resolution: {integrity: sha512-zuVdFrMJiuCDQUMCzQaD6KL28MjnqqN8XnAqiEq9PNm/hCPTSGfrXCOfwj1ow4LFb/tNymJPwsNbVePc1xFqrQ==}
dev: true

/@vitest/coverage-v8@1.4.0(vitest@1.4.0):
resolution: {integrity: sha512-4hDGyH1SvKpgZnIByr9LhGgCEuF9DKM34IBLCC/fVfy24Z3+PZ+Ii9hsVBsHvY1umM1aGPEjceRkzxCfcQ10wg==}
/@vitest/coverage-v8@1.5.0(vitest@1.5.0):
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'@vitest/coverage-v8' updated its peer dependency on 'vitest' to version 1.5.0. Make sure to verify compatibility.

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes involve updating the version of @vitest/coverage-v8 and vitest from 1.4.0 to 1.5.0 in both package.json and pnpm-lock.yaml files. All related dependencies in pnpm-lock.yaml file seems to have been updated accordingly. There seems to be a missing /v8-to-istanbul@9.2.0 dependency which might be an issue if it is required in the project

@@ -28,15 +28,15 @@
"@sentry/profiling-node": "7.110.0",
"@slonik/migrator": "0.12.0",
"@types/node": "20.12.7",
"@vitest/coverage-v8": "1.4.0",
"@vitest/coverage-v8": "1.5.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having updated the version of '@vitest/coverage-v8' in the package.json file, please ensure this new version doesn't introduce any breaking changes in your project.

"esbuild": "0.20.2",
"eslint": "8.57.0",
"eslint-config-prettier": "9.1.0",
"eslint-plugin-prettier": "5.1.3",
"npm-run-all2": "6.1.2",
"prettier": "3.2.5",
"typescript": "5.4.5",
"vitest": "1.4.0"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updating 'vitest' can possibly cause breaking changes in your code depending on what has been updated or deprecated in the new version.

@@ -58,8 +58,8 @@ importers:
specifier: 20.12.7
version: 20.12.7
'@vitest/coverage-v8':
specifier: 1.4.0
version: 1.4.0(vitest@1.4.0)
specifier: 1.5.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ensure that the updated version of '@vitest/coverage-v8' in pnpm-lock.yaml is consistent with package.json and it doesn't affect your project negatively.

@@ -82,8 +82,8 @@ importers:
specifier: 5.4.5
version: 5.4.5
vitest:
specifier: 1.4.0
version: 1.4.0(@types/node@20.12.7)
specifier: 1.5.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ensure that the updated 'vitest' version in pnpm-lock.yaml is consistent with the version in package.json, also check that the update does not break your project functionality.

@@ -1675,6 +1670,7 @@ packages:

/convert-source-map@2.0.0:
resolution: {integrity: sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg==}
dev: false

/cookie@0.6.0:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Check if /v8-to-istanbul@9.2.0 is not used anywhere in the project, otherwise its removal can lead to breaking changes in your code.

/@vitest/coverage-v8@1.4.0(vitest@1.4.0):
resolution: {integrity: sha512-4hDGyH1SvKpgZnIByr9LhGgCEuF9DKM34IBLCC/fVfy24Z3+PZ+Ii9hsVBsHvY1umM1aGPEjceRkzxCfcQ10wg==}
/@vitest/coverage-v8@1.5.0(vitest@1.5.0):
resolution: {integrity: sha512-1igVwlcqw1QUMdfcMlzzY4coikSIBN944pkueGi0pawrX5I5Z+9hxdTR+w3Sg6Q3eZhvdMAs8ZaF9JuTG1uYOQ==}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ensure that the change of 'vitest' version in peer dependencies doesn't affect other dependencies in your project.

@@ -1333,44 +1329,43 @@ packages:
std-env: 3.7.0
strip-literal: 2.1.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vitest has been updated in dependencies as well, make sure that all the features used from this package in your project are still available and work as expected.

'@types/istanbul-lib-coverage': 2.0.6
convert-source-map: 2.0.0
dev: true

/validator@13.11.0:
resolution: {integrity: sha512-Ii+sehpSfZy+At5nPdnyMhx78fEoPDkR2XW/zimHEL3MyGJQOCQ7WeP20jPYRz7ZCpcKLB21NxuXHF3bxjStBQ==}
engines: {node: '>= 0.10'}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vite-node version has been updated, checking for project compatibility and depending code is necessary.

Copy link

codecov bot commented Apr 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 42.50%. Comparing base (e7fe037) to head (70bb915).

✅ All tests successful. No failed tests found ☺️

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1884   +/-   ##
=======================================
  Coverage   42.50%   42.50%           
=======================================
  Files          83       83           
  Lines       10329    10329           
  Branches      161      195   +34     
=======================================
  Hits         4390     4390           
  Misses       5939     5939           
Flag Coverage Δ *Carryforward flag
core 100.00% <ø> (ø)
database 14.21% <ø> (ø)
gateway 46.84% <ø> (ø)
lobby 32.69% <ø> (ø)
login 24.06% <ø> (ø)
patch 87.28% <ø> (ø) Carriedforward from e7fe037
persona 27.94% <ø> (ø) Carriedforward from e7fe037
shard 96.87% <ø> (ø) Carriedforward from e7fe037
transactions 52.52% <ø> (ø) Carriedforward from e7fe037

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot merged commit 8c1980d into main Apr 11, 2024
15 checks passed
@renovate renovate bot deleted the renovate/vitest-monorepo branch April 11, 2024 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants