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 - autoclosed #330

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 17, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-v8 (source) ^1.1.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 force-pushed the renovate/vitest-coverage-v8-2.x branch 15 times, most recently from c63a956 to 6fb4b65 Compare July 23, 2024 14:59
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 14 times, most recently from c517bef to 9655979 Compare August 2, 2024 23:06
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 4 times, most recently from 3c8f518 to f535ff6 Compare January 1, 2025 21:22
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 8 times, most recently from 479adf9 to dc86e6a Compare January 9, 2025 12:45
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 7 times, most recently from 0291b56 to 01614e1 Compare January 16, 2025 23:25
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch 7 times, most recently from b051848 to 0ec9e0a Compare January 19, 2025 06:01
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch from 0ec9e0a to e86b00c Compare January 19, 2025 14:02
@renovate renovate bot changed the title chore(deps): update dependency @vitest/coverage-v8 to v2 chore(deps): update dependency @vitest/coverage-v8 to v2 - autoclosed Jan 19, 2025
@renovate renovate bot closed this Jan 19, 2025
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