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

Update dependency vitest to v2 #1303

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 6, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) 0.34.6 -> 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

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 - "after 9am on Wednesday" in timezone Europe/London, 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 added change: dependencies Updates to dependencies only release: skip Skips the release step when this pr is merged labels Dec 6, 2023
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from eadbdda to 6be7d68 Compare December 9, 2023 19:29
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 6be7d68 to 4804c14 Compare December 19, 2023 16:02
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from d39e2c5 to b031529 Compare January 5, 2024 09:05
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 49c25a8 to 8cf8257 Compare January 17, 2024 17:02
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 8cf8257 to f44347c Compare January 26, 2024 18:34
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from b16c9a9 to 69c997c Compare February 20, 2024 17:11
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 69c997c to 0f7ca4a Compare March 15, 2024 11:31
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 0f7ca4a to fb8dddd Compare April 11, 2024 18:11
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from bdd4ef0 to d22839e Compare April 30, 2024 11:18
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from d22839e to dccd5d9 Compare May 3, 2024 16:43
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from dccd5d9 to bd6b854 Compare July 8, 2024 13:35
@renovate renovate bot changed the title Update dependency vitest to v1 Update dependency vitest to v2 Jul 8, 2024
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 0a3e4e2 to 13d6226 Compare July 15, 2024 10:22
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 13d6226 to 7fd55fd Compare July 22, 2024 09:58
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 7fd55fd to 2b26cbe Compare July 31, 2024 13:14
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from db1f7b1 to 44cc24a Compare September 13, 2024 18:19
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 44cc24a to a7676e7 Compare October 2, 2024 17:12
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from a7676e7 to ec9993e Compare October 14, 2024 21:21
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from ec9993e to e16c1b5 Compare October 28, 2024 13:17
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from e16c1b5 to 7ed111e Compare November 13, 2024 19:59
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 7ed111e to 2c41ed3 Compare November 26, 2024 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change: dependencies Updates to dependencies only release: skip Skips the release step when this pr is merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants