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) #110

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 4, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/browser (source) ^0.29.7 -> ^2.0.0 age adoption passing confidence
@vitest/ui (source) ^0.29.7 -> ^2.0.0 age adoption passing confidence
vitest (source) ^0.29.7 -> ^2.0.0 age adoption passing confidence

Release Notes

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

v2.1.4

Compare Source

   🚀 Features

This patch release includes a non-breaking feature for the experimental Browser Mode that doesn't follow SemVer. If you want to avoid picking up releases like this, make sure to pin the Vitest version in your package.json. See npm's documentation about semver for more information.

   🐞 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.

Potential Breaking Change
  • workspace:
    • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6316 (afdcb)
    • This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
    • For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.
    • This change doesn't affect non-glob usage.
   🚀 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

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.0.1

Compare Source

   🐞 Bug Fixes

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 becomes conflicted, 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 2 times, most recently from 54eebe1 to 73ca322 Compare December 11, 2023 12:53
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 73ca322 to 76f7e5e Compare December 27, 2023 05:29
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from d6dd8d1 to ed35876 Compare January 8, 2024 03:02
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from d802c14 to dba97f6 Compare January 23, 2024 01:51
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 9c92d0f to cd36ac5 Compare February 15, 2024 03:34
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from d40b89c to c9b98a9 Compare February 25, 2024 13:12
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 6f2d0dd to 8a8561d Compare May 25, 2024 09:41
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 8a8561d to 6a2ebdc Compare July 8, 2024 14:29
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v1 (major) chore(deps): update vitest monorepo to v2 (major) Jul 8, 2024
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 7e398f2 to d1e9493 Compare August 6, 2024 11:13
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from d1e9493 to 588aa4f Compare August 28, 2024 09:00
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