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.1.4 #8

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

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-v8 (source) 2.0.4 -> 2.1.4 age adoption passing confidence
@vitest/ui (source) 2.0.4 -> 2.1.4 age adoption passing confidence
vitest (source) 2.0.4 -> 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

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

coderabbitai bot commented Jul 23, 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 changed the title chore(deps): update dependency @vitest/coverage-v8 to v2.0.4 chore(deps): update dependency @vitest/coverage-v8 to v2.0.4 - autoclosed Jul 26, 2024
@renovate renovate bot closed this Jul 26, 2024
@renovate renovate bot deleted the renovate/vitest-monorepo branch July 26, 2024 02:14
@renovate renovate bot changed the title chore(deps): update dependency @vitest/coverage-v8 to v2.0.4 - autoclosed chore(deps): update dependency @vitest/coverage-v8 to v2.0.4 Jul 31, 2024
@renovate renovate bot reopened this Jul 31, 2024
@renovate renovate bot restored the renovate/vitest-monorepo branch July 31, 2024 11:17
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e922bf4 to d8c5204 Compare July 31, 2024 12:24
@renovate renovate bot changed the title chore(deps): update dependency @vitest/coverage-v8 to v2.0.4 chore(deps): update vitest monorepo to v2.0.5 Jul 31, 2024
@pull-request-size pull-request-size bot added size/L and removed size/S labels Jul 31, 2024
Copy link

nx-cloud bot commented Jul 31, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 11ae2aa. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


✅ Successfully ran 1 target

Sent with 💌 from NxCloud.

@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.0.5 chore(deps): update vitest monorepo to v2.1.0 Sep 12, 2024
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.0 chore(deps): update vitest monorepo to v2.1.1 Sep 13, 2024
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.1 chore(deps): update vitest monorepo to v2.1.2 Oct 2, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d8c5204 to 5b9211a Compare October 7, 2024 08:53
Copy link

socket-security bot commented Oct 7, 2024

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

Package New capabilities Transitives Size Publisher
npm/@vitest/[email protected] Transitive: environment, filesystem, shell +64 10.9 MB vitestbot
npm/@vitest/[email protected] Transitive: filesystem +15 2.24 MB vitestbot
npm/[email protected] Transitive: environment, filesystem, shell, unsafe +32 4.16 MB antfu, oreanno, patak, ...1 more

🚮 Removed packages: npm/@vitest/[email protected], npm/@vitest/[email protected], npm/[email protected]

View full report↗︎

Copy link

codecov bot commented Oct 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.11%. Comparing base (da3039b) to head (11ae2aa).

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #8   +/-   ##
=======================================
  Coverage   60.11%   60.11%           
=======================================
  Files          19       19           
  Lines         682      682           
  Branches       68       68           
=======================================
  Hits          410      410           
  Misses        272      272           
Components Coverage Δ
Server 5.70% <ø> (ø)
Config ∅ <ø> (∅)
Web 79.32% <ø> (ø)
Utils 0.00% <ø> (ø)
All Tests 100.00% <ø> (ø)

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update da3039b...11ae2aa. Read the comment docs.

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 5b9211a to c4e1bda Compare October 7, 2024 08:59
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from c4e1bda to 11ae2aa Compare October 7, 2024 09:37
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.2 chore(deps): update vitest monorepo to v2.1.3 Oct 14, 2024
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.3 chore(deps): update vitest monorepo to v2.1.4 Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants