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 #397

Merged
merged 1 commit into from
Dec 13, 2024

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) ^1.0.0 -> ^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 12:09
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 10 times, most recently from 388fbcb to 178b57f Compare July 17, 2024 12:25
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 17 times, most recently from 5193627 to d9e19b1 Compare July 25, 2024 21:38
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch from d9e19b1 to a242f1d Compare July 26, 2024 01:59
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 11 times, most recently from 3164b20 to 9add5d0 Compare December 1, 2024 21:07
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 10 times, most recently from 2d30aca to 94a0b6c Compare December 7, 2024 22:23
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 5 times, most recently from e266d62 to 4dd2596 Compare December 13, 2024 16:26
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch from 4dd2596 to 20537e5 Compare December 13, 2024 22:22
@renovate renovate bot merged commit e7a4837 into main Dec 13, 2024
7 of 12 checks passed
@renovate renovate bot deleted the renovate/vitest-coverage-v8-2.x branch December 13, 2024 22:23
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