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 dependency @vitest/coverage-v8 to v2 #510

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

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-v8 (source) ^0.34.6 -> ^2.0.0 age adoption passing confidence

Release Notes

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

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate bot enabled auto-merge (squash) July 11, 2024 15:04
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 4 times, most recently from 9c0e6b9 to 970a369 Compare July 13, 2024 04:57
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 11 times, most recently from 2e8684f to c1c28f5 Compare August 5, 2024 05:27
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 13 times, most recently from 0abf633 to 19449fa Compare November 20, 2024 08:20
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 10 times, most recently from 794a1bd to a424272 Compare December 20, 2024 03:53
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 7 times, most recently from 003c1a1 to 7a286e5 Compare December 26, 2024 22:00
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 8 times, most recently from 7cbaa3e to c721c86 Compare January 6, 2025 10:34
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 3 times, most recently from 1778311 to cb681f9 Compare January 9, 2025 13:21
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch from cb681f9 to 572bee8 Compare January 10, 2025 00:28
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