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

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 (source) ^1.1.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 14 times, most recently from 9eb36d9 to 52b1df5 Compare July 23, 2024 15:01
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 15 times, most recently from fae8088 to 706fa5d Compare August 3, 2024 00:51
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 4 times, most recently from ed19dec to 8709164 Compare January 1, 2025 21:24
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 8 times, most recently from 234907d to 5180232 Compare January 9, 2025 12:47
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 7 times, most recently from d74b1d1 to df01290 Compare January 16, 2025 23:27
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 7 times, most recently from 4f6cee7 to 7b1d148 Compare January 19, 2025 06:03
@renovate renovate bot force-pushed the renovate/vitest-2.x branch from 7b1d148 to cbd6cc4 Compare January 19, 2025 14:04
@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
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