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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 11, 2024

This PR contains the following updates:

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

Copy link

changeset-bot bot commented Jul 11, 2024

⚠️ No Changeset found

Latest commit: de7adc4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/vitest-2.x branch 7 times, most recently from 5f6d054 to dbca47d Compare July 18, 2024 15:02
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 7 times, most recently from c87b34d to 6230c03 Compare July 25, 2024 17:44
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 9 times, most recently from f0f555e to 76c6f55 Compare August 3, 2024 15:08
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 4 times, most recently from 30cb84e to 502c921 Compare August 7, 2024 01:33
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 6 times, most recently from feae95c to efc4dfe Compare December 5, 2024 20:16
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 5 times, most recently from 669babd to 5869fa8 Compare December 14, 2024 06:22
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 6 times, most recently from 220e2cd to 7137306 Compare December 24, 2024 22:14
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 2 times, most recently from 3664b11 to 6b3eeda Compare December 31, 2024 15:09
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 2 times, most recently from 0c669a4 to 7fb11ed Compare January 9, 2025 21:52
@renovate renovate bot force-pushed the renovate/vitest-2.x branch 3 times, most recently from 4829237 to 7409d19 Compare January 16, 2025 21:20
@renovate renovate bot force-pushed the renovate/vitest-2.x branch from 7409d19 to 782f00c Compare January 19, 2025 09:31
@renovate renovate bot force-pushed the renovate/vitest-2.x branch from 782f00c to de7adc4 Compare January 19, 2025 09:33
@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
@renovate renovate bot deleted the renovate/vitest-2.x branch January 19, 2025 17:54
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