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

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

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/coverage-v8 (source) ^1.5.0 -> ^2.1.5 age adoption passing confidence
vitest (source) ^1.5.0 -> ^2.1.5 age adoption passing confidence

Release Notes

vitest-dev/vitest (@​vitest/coverage-v8)

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](https:/

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 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 4 times, most recently from cb54cbd to 185dd14 Compare July 15, 2024 13:04
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 90260e9 to 89f5d34 Compare July 23, 2024 01:13
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 89f5d34 to 156f403 Compare July 31, 2024 12:50
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 037bb5f to d72781a Compare September 13, 2024 19:36
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from d72781a to 130c71c Compare October 2, 2024 18:04
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 5d4dd63 to a5781ef Compare October 18, 2024 01:29
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 0c255ee to 00e8e94 Compare October 31, 2024 01:09
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 00e8e94 to 5c735d4 Compare November 13, 2024 16:36
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