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 v3 #79

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 -> ^3.0.5 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

v3.0.5

Compare Source

🚀 Features
🐞 Bug Fixes
View changes on GitHub

v3.0.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.3

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v3.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.1.9

Compare Source

   🚨 Breaking Changes
   🚀 Features

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: 816b64c

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.


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>, 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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 7b1be44 to 1e225df Compare December 24, 2023 15:31
@renovate renovate bot force-pushed the renovate/major-vitest branch 2 times, most recently from 9cc9c61 to 1955126 Compare January 7, 2024 15:33
@renovate renovate bot force-pushed the renovate/major-vitest branch from 1955126 to 2f40a1b Compare January 14, 2024 15:46
@renovate renovate bot force-pushed the renovate/major-vitest branch from 2f40a1b to 32c805c Compare January 21, 2024 16:43
@renovate renovate bot force-pushed the renovate/major-vitest branch from 32c805c to 5812b95 Compare January 28, 2024 17:57
@renovate renovate bot force-pushed the renovate/major-vitest branch 2 times, most recently from f3ea4da to adb8b48 Compare February 25, 2024 16:11
@renovate renovate bot force-pushed the renovate/major-vitest branch from adb8b48 to f64a18c Compare March 17, 2024 16:31
@renovate renovate bot force-pushed the renovate/major-vitest branch from f64a18c to f012327 Compare April 14, 2024 15:49
@renovate renovate bot force-pushed the renovate/major-vitest branch from f012327 to 3028f50 Compare April 28, 2024 16:37
@renovate renovate bot force-pushed the renovate/major-vitest branch from 3028f50 to f7b28b1 Compare May 5, 2024 16:38
@renovate renovate bot force-pushed the renovate/major-vitest branch from f7b28b1 to a1f3d15 Compare July 8, 2024 13:49
@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 b3d7350 to 453bbf7 Compare July 15, 2024 11:41
@renovate renovate bot force-pushed the renovate/major-vitest branch from 453bbf7 to 3cda07f Compare July 22, 2024 11:33
@renovate renovate bot force-pushed the renovate/major-vitest branch from 3cda07f to 8aa79d6 Compare August 4, 2024 16:18
@renovate renovate bot force-pushed the renovate/major-vitest branch from 8aa79d6 to 1a28b4d Compare September 15, 2024 15:31
@renovate renovate bot force-pushed the renovate/major-vitest branch from 1a28b4d to 3290198 Compare October 6, 2024 16:07
@renovate renovate bot force-pushed the renovate/major-vitest branch from 3290198 to 0e83160 Compare October 14, 2024 11:26
@renovate renovate bot force-pushed the renovate/major-vitest branch from 0e83160 to 5c3e68a Compare October 28, 2024 12:42
@renovate renovate bot force-pushed the renovate/major-vitest branch from 5c3e68a to 89125fc Compare November 17, 2024 15:58
@renovate renovate bot force-pushed the renovate/major-vitest branch from 89125fc to 2a23722 Compare December 1, 2024 15:14
@renovate renovate bot force-pushed the renovate/major-vitest branch 2 times, most recently from 4f5ed68 to b41bccc Compare December 8, 2024 15:29
@renovate renovate bot changed the title chore: update dependency vitest to v2 chore: update dependency vitest to v2 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/major-vitest branch December 8, 2024 18:37
@renovate renovate bot changed the title chore: update dependency vitest to v2 - autoclosed chore: update dependency vitest to v2 Dec 8, 2024
@renovate renovate bot reopened this Dec 8, 2024
@renovate renovate bot force-pushed the renovate/major-vitest branch from b41bccc to f3bf05d Compare January 19, 2025 17:13
@renovate renovate bot changed the title chore: update dependency vitest to v2 chore: update dependency vitest to v3 Jan 19, 2025
@renovate renovate bot force-pushed the renovate/major-vitest branch from f3bf05d to 748c287 Compare January 26, 2025 16:47
@renovate renovate bot force-pushed the renovate/major-vitest branch from 748c287 to 8a17775 Compare February 3, 2025 13:53
@renovate renovate bot changed the title chore: update dependency vitest to v3 chore: update dependency vitest to v2 Feb 3, 2025
@renovate renovate bot force-pushed the renovate/major-vitest branch from 8a17775 to 816b64c Compare February 9, 2025 17:51
@renovate renovate bot changed the title chore: update dependency vitest to v2 chore: update dependency vitest to v3 Feb 9, 2025
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