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: update dependency vitest to v2 #101

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 10, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) ^0.34.6 -> ^2.1.8 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

v2.1.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.6

Compare Source

🚀 Features

  • Support VIte 6
    View changes on GitHub

v2.1.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.3

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

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](https://redirect.gith


Configuration

📅 Schedule: Branch creation - "after 10am on monday,before 5pm on monday" in timezone Asia/Tokyo, 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

changeset-bot bot commented Dec 10, 2023

⚠️ No Changeset found

Latest commit: a883dda

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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 Dec 10, 2023

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>, 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 branch from b659230 to 6766702 Compare December 10, 2023 16:53
@renovate renovate bot force-pushed the renovate/major-vitest branch 3 times, most recently from 982c5f1 to c806f73 Compare December 24, 2023 18:45
@renovate renovate bot force-pushed the renovate/major-vitest branch from c806f73 to 0e2e281 Compare December 31, 2023 15:06
@renovate renovate bot force-pushed the renovate/major-vitest branch from 0e2e281 to 28b52a4 Compare January 7, 2024 16:28
@renovate renovate bot force-pushed the renovate/major-vitest branch 2 times, most recently from ac62cba to 7b04831 Compare January 21, 2024 16:31
@renovate renovate bot force-pushed the renovate/major-vitest branch 2 times, most recently from 1b04e2d to 7297c9a Compare January 28, 2024 18:19
@renovate renovate bot force-pushed the renovate/major-vitest branch from 7297c9a to 1e8ac77 Compare February 18, 2024 15:28
@renovate renovate bot force-pushed the renovate/major-vitest branch from 1e8ac77 to 197e43e Compare February 25, 2024 16:27
@renovate renovate bot force-pushed the renovate/major-vitest branch from 197e43e to efccd6a Compare March 17, 2024 17:16
@renovate renovate bot force-pushed the renovate/major-vitest branch from efccd6a to 3a24b13 Compare March 24, 2024 23:15
@renovate renovate bot force-pushed the renovate/major-vitest branch from 3a24b13 to 099437f Compare April 14, 2024 15:47
@renovate renovate bot force-pushed the renovate/major-vitest branch 2 times, most recently from dd1d78d to 7dbb26f Compare May 5, 2024 16:20
@renovate renovate bot force-pushed the renovate/major-vitest branch from 7dbb26f to ec08594 Compare July 8, 2024 13:24
@renovate renovate bot changed the title chore: update dependency vitest to v1 chore: update dependency vitest to v2 Jul 8, 2024
@renovate renovate bot force-pushed the renovate/major-vitest branch 2 times, most recently from 4100f88 to d3def33 Compare July 15, 2024 13:30
@renovate renovate bot force-pushed the renovate/major-vitest branch from d3def33 to 4c25038 Compare July 22, 2024 10:35
@renovate renovate bot force-pushed the renovate/major-vitest branch from 4c25038 to c0cd192 Compare August 4, 2024 16:33
@renovate renovate bot force-pushed the renovate/major-vitest branch from c0cd192 to 4d39e69 Compare September 15, 2024 15:16
@renovate renovate bot force-pushed the renovate/major-vitest branch from 4d39e69 to dc82036 Compare October 6, 2024 16:22
@renovate renovate bot force-pushed the renovate/major-vitest branch from dc82036 to f186e3f Compare October 20, 2024 15:32
@renovate renovate bot force-pushed the renovate/major-vitest branch from f186e3f to 9491912 Compare October 28, 2024 12:39
@renovate renovate bot force-pushed the renovate/major-vitest branch from 9491912 to f2997b3 Compare November 17, 2024 16:57
@renovate renovate bot force-pushed the renovate/major-vitest branch 2 times, most recently from 18646f8 to 6b08816 Compare December 2, 2024 10:57
@renovate renovate bot force-pushed the renovate/major-vitest branch from 6b08816 to a883dda Compare December 2, 2024 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants