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

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 12, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/browser (source) 0.25.8 -> 2.1.5 age adoption passing confidence
vitest (source) 0.24.5 -> 2.1.5 age adoption passing confidence

Release Notes

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

v2.1.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

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

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.

Copy link

vercel bot commented Dec 12, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
design-system ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 13, 2024 3:48pm

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 6ffda6f to 5f64174 Compare December 12, 2023 19:42
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 5f64174 to 29dda6f Compare December 14, 2023 06:25
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 29dda6f to 62df06d Compare December 15, 2023 05:56
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 62df06d to e8e0259 Compare December 19, 2023 17:08
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from e8e0259 to d364bc3 Compare December 21, 2023 04:39
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from d364bc3 to 8bf2faf Compare December 21, 2023 07:28
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 8bf2faf to a4a9b96 Compare December 31, 2023 15:11
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from a4a9b96 to 31478e1 Compare January 2, 2024 07:51
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from c2718a8 to 217f157 Compare January 2, 2024 09:28
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 217f157 to e81707f Compare January 3, 2024 03:50
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from e81707f to 7900b1e Compare January 3, 2024 05:25
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 7900b1e to de986b8 Compare January 3, 2024 06:26
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from de986b8 to 849e1ca Compare January 4, 2024 04:24
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 1f6bebc to 34e5071 Compare September 30, 2024 05:33
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 34e5071 to ae51222 Compare October 2, 2024 06:37
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from ae51222 to aa93ef7 Compare October 2, 2024 19:38
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from aa93ef7 to 2a1ed75 Compare October 7, 2024 03:03
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 2a1ed75 to 4bec7d6 Compare October 7, 2024 03:55
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 4bec7d6 to 7b66817 Compare October 10, 2024 05:06
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 7b66817 to 87b222e Compare October 10, 2024 06:05
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from d32b27f to cbe1e48 Compare October 10, 2024 09:32
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from cbe1e48 to 7144dbf Compare October 14, 2024 20:55
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 7144dbf to add7d6d Compare October 22, 2024 05:36
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from add7d6d to c3e9e81 Compare October 28, 2024 13:50
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from c3e9e81 to c289754 Compare November 13, 2024 07:20
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