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

Merged
merged 1 commit into from
Oct 28, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 8, 2024

This PR contains the following updates:

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

Release Notes

vitest-dev/vitest (vitest)

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
    View changes on GitHub

v2.0.0

Compare Source

Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.

🚨 Breaking Changes

Configuration

📅 Schedule: Branch creation - "before 12pm on Sunday" (UTC), Automerge - At any time (no schedule defined).

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

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 label Jul 8, 2024
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from f0970b3 to 7b3cc11 Compare July 27, 2024 06:48
@renovate renovate bot requested a review from kyranet as a code owner July 27, 2024 06:48
@renovate renovate bot changed the title chore: bump up vitest version to v2 chore(deps): update dependency vitest to v2 Jul 27, 2024
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 7b3cc11 to 144eb5c Compare July 31, 2024 11:09
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from aa1125b to 41aebdd Compare September 13, 2024 20:14
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 41aebdd to cdec1c5 Compare October 2, 2024 19:19
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from cdec1c5 to 1cb5519 Compare October 14, 2024 19:33
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 1cb5519 to 2392e83 Compare October 28, 2024 14:03
@kyranet kyranet merged commit 43aada2 into main Oct 28, 2024
29 checks passed
@kyranet kyranet deleted the renovate/major-vitest-monorepo branch October 28, 2024 15:10
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.

1 participant