Skip to content

Update dependency vitest to v2#316

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-2-vitest-monorepo
Open

Update dependency vitest to v2#316
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-2-vitest-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Apr 27, 2025 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vitest (source) 0.33.0 → 2.1.9 age confidence

Release Notes

vitest-dev/vitest (vitest)

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

v2.0.5

Compare Source

   🚀 Features
  • Introduce experimental reported tasks  -  by @​sheremet-va in #​6149 (13d85)
    • This is part of the experimental API and doesn't follow semver. We are hoping to stabilize it for 2.1. If you are working with custom reporters, give this a go!
   🐞 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

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 this update 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 added the renovate Created by Renovate label Apr 27, 2025
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Apr 27, 2025 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nuxt/test-utils@3.6.5
npm error Found: vitest@2.1.9
npm error node_modules/vitest
npm error   dev vitest@"2.1.9" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional vitest@"^0.30.0 || ^0.31.0 || ^0.32.0 || ^0.33.0" from @nuxt/test-utils@3.6.5
npm error node_modules/@nuxt/test-utils
npm error   dev @nuxt/test-utils@"3.6.5" from the root project
npm error
npm error Conflicting peer dependency: vitest@0.33.0
npm error node_modules/vitest
npm error   peerOptional vitest@"^0.30.0 || ^0.31.0 || ^0.32.0 || ^0.33.0" from @nuxt/test-utils@3.6.5
npm error   node_modules/@nuxt/test-utils
npm error     dev @nuxt/test-utils@"3.6.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-03-13T11_11_56_991Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-13T11_11_56_991Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-2-vitest-monorepo branch 4 times, most recently from 5190785 to 76cac48 Compare April 27, 2025 12:50
@netlify
Copy link
Copy Markdown

netlify bot commented Apr 27, 2025 •
edited
Loading

❌ Deploy Preview for anohi-no-tweet failed.

Name Link
🔨 Latest commit 20053ab
🔍 Latest deploy log https://app.netlify.com/projects/anohi-no-tweet/deploys/688b58513942b80008ff3f36

@renovate renovate bot force-pushed the renovate/major-2-vitest-monorepo branch 7 times, most recently from 4df2475 to ff5d1c0 Compare April 28, 2025 09:30
@renovate renovate bot force-pushed the renovate/major-2-vitest-monorepo branch 3 times, most recently from 518278d to 492cfc4 Compare July 31, 2025 11:44
@renovate renovate bot force-pushed the renovate/major-2-vitest-monorepo branch from 492cfc4 to 20053ab Compare July 31, 2025 11:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

renovate Created by Renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants