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 v2 #331

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 8, 2024

This PR contains the following updates:

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

Release Notes

vitest-dev/vitest (vitest)

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

v2.0.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.2

Compare Source

v2.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.0

Compare 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
🚀 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 was generated by Mend Renovate. View the repository job log.

Copy link

codesandbox bot commented Jul 8, 2024

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

Copy link

changeset-bot bot commented Jul 8, 2024

⚠️ No Changeset found

Latest commit: 91de2ce

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

coderabbitai bot commented Jul 8, 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.

Walkthrough

The primary change involves updating the vitest testing framework from version 1.6.0 to 2.0.5 in the package.json file. This upgrade may introduce new features, enhancements, or bug fixes that could impact the project's performance and functionality. Notably, compatibility with Node.js remains unchanged, ensuring that the environment continues to support the updated package without any interruptions.

Changes

Files Change Summary
package.json Updated "vitest" from 1.6.0 to 2.0.5; engines unchanged.

Poem

In a garden of code, a rabbit hops bright,
Upgrading vitest brings new delight!
Bugs vanish like shadows, features take flight,
With hops of improvement, we code through the night.
🐇✨ Let's celebrate changes that make our hearts sing,
For joy in our testing is a wonderful thing!


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>, please review it.
    -- 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    -- @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.

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 4 times, most recently from 7cef717 to b96b89c Compare July 15, 2024 12:42
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 7d0ffce to 83575ec Compare July 22, 2024 09:20
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from b5789fd to 9b486aa Compare July 31, 2024 11:20
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 5744458 to 45dfac3 Compare August 7, 2024 21:44
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9bf4988 and 45dfac3.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (1)
  • package.json (1 hunks)
Additional comments not posted (1)
package.json (1)

52-52: Verify compatibility with Vitest v2.0.5.

The vitest version has been updated from 1.6.0 to 2.0.5. Ensure that the test suite is compatible with this new version, as there may be breaking changes or new features that affect test execution.

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 45dfac3 to 305bd3c Compare August 12, 2024 03:37
Copy link

socket-security bot commented Aug 12, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/vitest@2.1.1 Transitive: environment, filesystem, shell, unsafe +32 4.04 MB antfu, oreanno, patak, ...1 more

🚮 Removed packages: npm/vitest@1.6.0

View full report↗︎

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 305bd3c to 71416a4 Compare August 15, 2024 18:32
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 45dfac3 and 71416a4.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (1)
  • package.json (1 hunks)
Additional comments not posted (1)
package.json (1)

52-52: Verify compatibility of Vitest version 2.0.5.

The update to Vitest version 2.0.5 may introduce new features or breaking changes. Ensure that all tests pass and that the updated version is compatible with the existing codebase.

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 3a93f81 to 9bedcf5 Compare August 19, 2024 14:02
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 71416a4 and 9bedcf5.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (1)
  • package.json (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • package.json

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from c95be73 to 93a73b8 Compare August 26, 2024 05:07
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from c5ed8ff to 50b1839 Compare September 9, 2024 03:20
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 4c29790 to 88beaac Compare September 12, 2024 17:31
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 5 times, most recently from 71ff69a to 5b312bd Compare September 17, 2024 14:55
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 5b312bd to 91de2ce Compare September 20, 2024 21:28
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.

0 participants