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

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/coverage-v8 (source) ^0.34.6 -> ^2.1.4 age adoption passing confidence
@vitest/ui (source) ^0.34.7 -> ^2.1.4 age adoption passing confidence
vitest (source) ^0.34.6 -> ^2.1.4 age adoption passing confidence

Release Notes

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

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

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "before 4am" in timezone Asia/Shanghai.

🚦 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

codecov bot commented Dec 10, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.62%. Comparing base (a460eea) to head (966d52b).

❗ Current head 966d52b differs from pull request most recent head 438c94f. Consider uploading reports for the commit 438c94f to get more accurate results

Additional details and impacted files
@@             Coverage Diff              @@
##              main     #146       +/-   ##
============================================
- Coverage   100.00%   89.62%   -10.38%     
============================================
  Files            5        6        +1     
  Lines           95      106       +11     
  Branches        13       14        +1     
============================================
  Hits            95       95               
- Misses           0       10       +10     
- Partials         0        1        +1     

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

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from fda50ab to 2098ce6 Compare December 19, 2023 16:36
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 9871e99 to e6a534d Compare January 5, 2024 10:25
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 56b88b7 to 06bea4a Compare January 17, 2024 16:51
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 06bea4a to 5983e51 Compare January 26, 2024 20:44
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 591d0b8 to e2b860f Compare February 20, 2024 16:56
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from e2b860f to 966d52b Compare March 15, 2024 13:32
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 966d52b to c6a0ce6 Compare April 11, 2024 18:48
Copy link

coderabbitai bot commented Apr 11, 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>, 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 3 times, most recently from 3057e39 to ba35c01 Compare April 30, 2024 09:17
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from ba35c01 to 438c94f Compare May 3, 2024 15:56
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 438c94f to daaf67d Compare July 8, 2024 13:39
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v1 (major) chore(deps): update vitest monorepo to v2 (major) Jul 8, 2024
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from cb89633 to 871a338 Compare July 15, 2024 10:55
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 871a338 to d5fd7c4 Compare July 22, 2024 14:43
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from d5fd7c4 to 2080d27 Compare July 31, 2024 13:30
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 0b4efc4 to d42e42d Compare September 13, 2024 17:28
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from d42e42d to 6dfd0fc Compare October 2, 2024 16:45
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 6dfd0fc to d74038a Compare October 14, 2024 21:07
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from d74038a to dd918c9 Compare October 28, 2024 16:47
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