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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 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.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
    View changes on GitHub

v2.0.2

Compare Source

v2.0.1

Compare Source

   🐞 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 added the dependencies Pull requests that update a dependency file label Sep 11, 2024
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 25 times, most recently from b8b662a to 79adf25 Compare September 17, 2024 03:10
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 4 times, most recently from 1966c2c to 12fe8cb Compare September 20, 2024 16:28
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 16 times, most recently from 30a9b5a to 4cb86a3 Compare November 22, 2024 14:00
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 7 times, most recently from c2c5f51 to 27898de Compare November 25, 2024 22:52
@renovate renovate bot force-pushed the renovate/vitest-2.x branch from 27898de to c054ea1 Compare November 26, 2024 05:32
@renovate renovate bot enabled auto-merge (squash) November 28, 2024 16:44
@renovate renovate bot changed the title chore(deps): update dependency vitest to v2 chore(deps): update dependency vitest to v2 - autoclosed Nov 28, 2024
@renovate renovate bot closed this Nov 28, 2024
auto-merge was automatically disabled November 28, 2024 17:03

Pull request was closed

@renovate renovate bot deleted the renovate/vitest-2.x branch November 28, 2024 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants