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 v2.1.1 #2095

Merged
merged 1 commit into from
Sep 15, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 26, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-v8 (source) 2 -> 2.1.1 age adoption passing confidence
@vitest/coverage-v8 (source) 2.0.5 -> 2.1.1 age adoption passing confidence
vitest (source) ^2.0.5 -> ^2.1.1 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

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

v2.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.0

Compare Source

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

  await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()

  const [firstPost] = screen.getByRole('listitem').all()

  await firstPost.getByRole('button', { name: 'Delete' }).click()

  expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

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 page object from @vitest/browser/context.

   🚀 Features
   🐞 Bug Fixes
    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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Aug 26, 2024

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

Copy link

coderabbitai bot commented Aug 26, 2024

Important

Review skipped

Bot user detected.

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

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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

@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.

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.

pnpm-lock.yaml Outdated
@@ -10,7 +10,7 @@ importers:
dependencies:
'@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])
Copy link

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.

pnpm-lock.yaml Outdated
@@ -79,7 +79,7 @@
version: link:packages/transactions
sequelize:
specifier: ^6.35.2
Copy link

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.

pnpm-lock.yaml Outdated
dependencies:
adminjs: 7.8.11(@types/[email protected])
escape-regexp: 0.0.1
sequelize: 6.37.3([email protected])
sequelize: 6.37.3

'@ampproject/[email protected]':
Copy link

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.

pnpm-lock.yaml Outdated
@@ -6034,11 +6034,11 @@
- react-is
- supports-color

Copy link

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.

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

@@ -32,7 +32,7 @@
},
"description": "",
"devDependencies": {
"@vitest/coverage-v8": "2",
"@vitest/coverage-v8": "2.0.5",
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 '@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.

pnpm-lock.yaml Outdated
@@ -10,7 +10,7 @@ importers:
dependencies:
'@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])
Copy link

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.

pnpm-lock.yaml Outdated
@@ -79,7 +79,7 @@
version: link:packages/transactions
sequelize:
specifier: ^6.35.2
Copy link

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.

pnpm-lock.yaml Outdated
dependencies:
adminjs: 7.8.11(@types/[email protected])
escape-regexp: 0.0.1
sequelize: 6.37.3([email protected])
sequelize: 6.37.3

'@ampproject/[email protected]':
Copy link

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.

Copy link

deepsource-io bot commented Aug 26, 2024

Here's the code health analysis summary for commits 7650d0a..c671836. 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.

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b967710 to 2e00a69 Compare August 27, 2024 12:11
Copy link

codecov bot commented Aug 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 29.58%. Comparing base (4c999f0) to head (c671836).
Report is 16 commits behind head on dev.

✅ 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           
Flag Coverage Δ
cli 7.14% <ø> (ø)
connection 22.42% <ø> (ø)
database 30.76% <ø> (ø)
gateway 23.46% <ø> (ø)
lobby 14.37% <ø> (ø)
login 7.14% <ø> (ø)
mcots 10.62% <ø> (ø)
nps 15.88% <ø> (ø)
patch 65.04% <ø> (ø)
persona 19.45% <ø> (ø)
sessions 91.98% <ø> (ø)
shard 47.71% <ø> (ø)
shared 23.71% <ø> (ø)
shared-packets 2.64% <ø> (ø)
transactions 60.54% <ø> (ø)

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

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 9 times, most recently from 4712886 to 5763334 Compare August 27, 2024 17:05
@renovate renovate bot changed the title chore(deps): update dependency @vitest/coverage-v8 to v2.0.5 chore(deps): update vitest monorepo to v2.1.0 Sep 12, 2024
@pull-request-size pull-request-size bot added size/L and removed size/M labels Sep 12, 2024
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.0 chore(deps): update vitest monorepo to v2.1.1 Sep 13, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 230d2b7 to 8773659 Compare September 15, 2024 13:31
Copy link

sonarcloud bot commented Sep 15, 2024

@renovate renovate bot added this pull request to the merge queue Sep 15, 2024
Merged via the queue into dev with commit 673eef2 Sep 15, 2024
14 checks passed
@renovate renovate bot deleted the renovate/vitest-monorepo branch September 15, 2024 14:43
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