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 v3 (major) #94

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 9, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-istanbul (source) 1.6.0 -> 3.0.3 age adoption passing confidence
vitest (source) 1.6.0 -> 3.0.3 age adoption passing confidence

Release Notes

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

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

Vitest 3 is here! There are a few breaking changes, but we expect the migration to be smooth. 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
    View changes on GitHub

v2.1.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

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

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.4

Compare Source

   🚀 Features

This patch release includes a non-breaking feature for the experimental Browser Mode that doesn't follow SemVer. If you want to avoid picking up releases like this, make sure to pin the Vitest version in your package.json. See npm's documentation about semver for more information.

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.3

Compare Source

   🐞 Bug Fixes

Configuration

📅 Schedule: Branch creation - "before 4am" (UTC), Automerge - "before 4am" (UTC).

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

vercel bot commented Jul 9, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
repository-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 21, 2025 2:09pm

Copy link

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


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.

Copy link

github-actions bot commented Jul 9, 2024

Coverage Report for packages/repository

Status Category Percentage Covered / Total
🟢 Lines 96.83% (🎯 80%) 153 / 158
🟢 Statements 97.02% (🎯 80%) 163 / 168
🟢 Functions 95.71% (🎯 80%) 67 / 70
🟢 Branches 92.47% (🎯 80%) 86 / 93
File CoverageNo changed files found.
Generated in workflow #355 for commit deb7d1b by the Vitest Coverage Report Action

@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from 2c08080 to b9a6a6f Compare July 10, 2024 16:37
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from b9a6a6f to 6d5d130 Compare July 15, 2024 14:51
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from 6d5d130 to 344bcde Compare July 22, 2024 09:39
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from 344bcde to 594b5d6 Compare July 31, 2024 11:02
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from 594b5d6 to 1966290 Compare September 12, 2024 15:30
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from 1966290 to d8cc6fe Compare September 13, 2024 16:35
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from d8cc6fe to 2ee8eed Compare October 2, 2024 18:29
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from 2ee8eed to 2170f58 Compare October 14, 2024 11:17
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from 2170f58 to a649b88 Compare October 14, 2024 20:59
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from a649b88 to 9b609b6 Compare October 28, 2024 12:54
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from 9b609b6 to 526135b Compare November 13, 2024 16:05
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from 526135b to 8fd86b0 Compare November 26, 2024 12:58
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from 8fd86b0 to f2bcebb Compare December 2, 2024 12:52
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from f2bcebb to 156a6c5 Compare December 2, 2024 17:26
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from 156a6c5 to d704620 Compare January 16, 2025 17:45
@renovate renovate bot changed the title ⬆️ chore(deps): Update vitest monorepo to v2 (major) ⬆️ chore(deps): Update vitest monorepo to v3 (major) Jan 16, 2025
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from d704620 to e6fe338 Compare January 16, 2025 20:27
@renovate renovate bot force-pushed the deps/major-vitest-monorepo branch from e6fe338 to 6f3291b Compare January 17, 2025 16:36
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