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

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

This PR contains the following updates:

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

Release Notes

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

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
    View changes on GitHub

v2.0.2

Compare Source

v2.0.1

Compare Source

   🐞 Bug Fixes

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, 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 (rebase) July 12, 2024 16:47
Copy link

vercel bot commented Jul 12, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
blog ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 15, 2024 3:28pm

@renovate renovate bot requested a review from t-yng July 12, 2024 18:35
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch from 4a2905b to a69ced2 Compare July 19, 2024 15:49
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch from a69ced2 to 1fcd460 Compare July 26, 2024 16:48
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch from 1fcd460 to 1b83805 Compare August 2, 2024 15:13
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch from 1b83805 to 9f23016 Compare August 11, 2024 02:13
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch from 9f23016 to dfb0e16 Compare September 13, 2024 16:13
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch from dfb0e16 to 420408c Compare October 4, 2024 15:03
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch from 420408c to 4d0df57 Compare October 18, 2024 15:20
@renovate renovate bot force-pushed the renovate/vitest-coverage-v8-2.x branch from 4d0df57 to 8ec1495 Compare November 1, 2024 15:20
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