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 to v2 - autoclosed #335

Closed
wants to merge 1 commit into 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 (source) ^1.0.0 -> ^2.0.0 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

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

   🚀 Features
   🐞 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-2.x branch 6 times, most recently from b52ac21 to 9cfd67e Compare July 13, 2024 03:33
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 17 times, most recently from a59e3a5 to d2c3ace Compare August 12, 2024 19:18
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 6 times, most recently from bf0d062 to de9790e Compare November 19, 2024 10:15
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 24 times, most recently from 3d1e0dc to b5ed6fe Compare November 25, 2024 00:34
@renovate renovate bot force-pushed the renovate/vitest-2.x branch from b5ed6fe to f8d8b07 Compare November 25, 2024 04:07
@renovate renovate bot changed the title chore(deps): update dependency vitest to v2 chore(deps): update dependency vitest to v2 - autoclosed Jan 19, 2025
@renovate renovate bot closed this Jan 19, 2025
@renovate renovate bot deleted the renovate/vitest-2.x branch January 19, 2025 14:27
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