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 vitest monorepo to v2 (major) #488

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 18, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/ui (source) 1.6.0 -> 2.1.7 age adoption passing confidence
vitest (source) 1.6.0 -> 2.1.7 age adoption passing confidence

Release Notes

vitest-dev/vitest (@​vitest/ui)

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

   🐞 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 these updates 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 force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 4e141d1 to feb910e Compare August 20, 2024 06:23
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 0e86689 to 9c2bdbd Compare September 13, 2024 17:23
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 9c2bdbd to 804fd4d Compare October 2, 2024 18:19
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 804fd4d to ccb2253 Compare October 14, 2024 17:24
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from ccb2253 to 656d081 Compare October 28, 2024 12:49
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 656d081 to b71bb5d Compare November 13, 2024 16:36
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from b71bb5d to 76f4329 Compare November 26, 2024 15:32
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 76f4329 to 703ae25 Compare December 2, 2024 10:24
Copy link

sonarcloud bot commented Dec 2, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants