Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Sep 12, 2024

This PR contains the following updates:

Package Change Age Confidence
@vitest/coverage-v8 (source) 2.0.5 -> 2.1.9 age confidence
vitest (source) 2.0.5 -> 2.1.9 age confidence

Release Notes

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

v2.1.9

Compare Source

This release includes security patches for:

   🐞 Bug Fixes
    View changes on GitHub

v2.1.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.7

Compare Source

   🐞 Bug Fixes
  • Revert support for Vite 6  -  by @​sheremet-va (fbe5c)
    • This introduced some breaking changes (#​6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.
    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

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

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.

@changeset-bot
Copy link

changeset-bot bot commented Sep 12, 2024

⚠️ No Changeset found

Latest commit: 2d585fb

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 changed the title chore(deps): update vitest monorepo to v2.1.0 chore(deps): update vitest monorepo to v2.1.1 Sep 14, 2024
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.1 chore(deps): update vitest monorepo to v2.1.2 Oct 4, 2024
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.2 chore(deps): update vitest monorepo to v2.1.3 Oct 15, 2024
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.3 chore(deps): update vitest monorepo to v2.1.4 Oct 28, 2024
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.4 chore(deps): update vitest monorepo to v2.1.5 Nov 14, 2024
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.5 chore(deps): update vitest monorepo to v2.1.6 Nov 26, 2024
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.6 chore(deps): update vitest monorepo to v2.1.8 Dec 4, 2024
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from f2d92a0 to cda3273 Compare January 24, 2025 08:07
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from d10ccb9 to c1fe213 Compare February 5, 2025 08:20
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v2.1.8 chore(deps): update vitest monorepo to v2.1.9 Feb 5, 2025
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from c1fe213 to 28da3e7 Compare February 9, 2025 23:31
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 1a28412 to b6f7f75 Compare March 12, 2025 04:08
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b6f7f75 to 1e6df5e Compare March 17, 2025 23:51
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 1e6df5e to 3404a22 Compare April 3, 2025 03:54
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 3404a22 to 357cede Compare April 11, 2025 20:17
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 357cede to fe4053b Compare April 26, 2025 15:53
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from fe4053b to 455ba33 Compare May 23, 2025 04:14
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 0715dfd to 13bd029 Compare June 6, 2025 14:57
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 13bd029 to 94783b2 Compare June 28, 2025 23:54
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 94783b2 to 30a3eb2 Compare July 6, 2025 08:03
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 30a3eb2 to 4862c2d Compare August 13, 2025 23:46
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 4862c2d to 4bda8fc Compare August 23, 2025 07:25
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 4bda8fc to 8674c6c Compare September 1, 2025 12:08
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 8674c6c to 0250cb5 Compare September 26, 2025 20:22
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 0250cb5 to 2d585fb Compare October 25, 2025 07:30
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.

1 participant