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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update dependency vitest to ^2.1.6 #61

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dependency vitest to ^2.1.6 #61

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 12, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) ^2.0.5 -> ^2.1.6 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 changed the title chore(deps): update dependency vitest to ^2.1.0 chore(deps): update dependency vitest to ^2.1.1 Sep 13, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 852fabf to 0df9d4c Compare October 2, 2024 19:53
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^2.1.1 chore(deps): update dependency vitest to ^2.1.2 Oct 2, 2024
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^2.1.2 chore(deps): update dependency vitest to ^2.1.3 Oct 14, 2024
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^2.1.3 chore(deps): update dependency vitest to ^2.1.4 Oct 28, 2024
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^2.1.4 chore(deps): update dependency vitest to ^2.1.5 Nov 13, 2024
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^2.1.5 chore(deps): update dependency vitest to ^2.1.6 Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants