Skip to content

chore(deps-dev): bump vitest from 1.6.1 to 3.2.6#29

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest-3.2.6
Open

chore(deps-dev): bump vitest from 1.6.1 to 3.2.6#29
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest-3.2.6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 8, 2026

Copy link
Copy Markdown

Bumps vitest from 1.6.1 to 3.2.6.

Release notes

Sourced from vitest's releases.

v3.2.6

   🐞 Bug Fixes

    View changes on GitHub

v3.2.5

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v3.2.4

   🐞 Bug Fixes

    View changes on GitHub

v3.2.3

   🚀 Features

... (truncated)

Commits
  • b6d56f8 chore: release v3.2.6
  • 16f120d fix: pin last supported vite-node version
  • 2cbad0a chore: release v3.2.5
  • 385a1ae fix(browser): disable client cdp API when allowWrite/allowExec: false [ba...
  • af88b1f feat(api): add allowWrite and allowExec options to api [backport to v3]...
  • c666d14 chore: release v3.2.4
  • 8a18c8e fix(cli): throw error when --shard x/\<count> exceeds count of test files (#...
  • 8abd7cc chore(deps): update tinypool (#8174)
  • 93f3200 fix(deps): update all non-major dependencies (#8123)
  • 0c3be6f fix(coverage): ignore SCSS in browser mode (#8161)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for vitest since your current version.


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Note

Medium Risk
Major-version test tooling jump may break tests or require config tweaks; runtime library surface is unchanged.

Overview
Upgrades the dev test runner Vitest from 1.6.1 to 3.2.6 in package.json, with pnpm-lock.yaml refreshed for the new @vitest/* stack (e.g. chai 5, vite-node 3.2.4, tinypool 1.x) and removal of Vitest 1–era transitive packages.

No application source or Vitest config files are changed; test / test:watch still invoke vitest as before. Reviewers should confirm pnpm test (and CI) pass under the major bump, since Vitest 3 can differ in APIs and defaults from v1.

Reviewed by Cursor Bugbot for commit ea2a3a7. Bugbot is set up for automated code reviews on this repo. Configure here.

Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 1.6.1 to 3.2.6.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v3.2.6/packages/vitest)

---
updated-dependencies:
- dependency-name: vitest
  dependency-version: 3.2.6
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jun 8, 2026

@meroreviewer meroreviewer Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 AI Code Reviewer

Reviewed by 2 agents | Quality score: 55% | Review time: 55.3s

🟡 1 warnings, 💡 1 suggestions. See inline comments.


🤖 Generated by AI Code Reviewer | Review ID: review-d502ca7d

Comment thread package.json
"typescript": "^5.3.0",
"vite": "^5.4.21",
"vitest": "^1.0.0"
"vitest": "^3.2.6"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Major version bump (v1 → v3) without explicit compatibility verification

The vitest dependency is being bumped from ^1.0.0 (resolved to 1.6.1) to ^3.2.6 — a two-major-version jump. Vitest v2 and v3 introduced breaking changes (e.g., new pool defaults, changed snapshot serialization, updated expect API, new @vitest/mocker package, removal of local-pkg, acorn-walk, execa from the dependency tree, and changed node engine requirements from ^18.0.0 || >=20.0.0 to ^18.0.0 || ^20.0.0 || >=22.0.0). There is no evidence in the diff of any test suite updates, vitest config changes, or CI verification that existing tests still pass under v3. The PR description is purely a Dependabot bump with no mention of test results.

Suggested fix:

Before merging, run `pnpm test` locally and in CI to confirm all tests pass. Review the vitest v2 and v3 migration guides for breaking changes. Check `vitest.config.*` (not present in the diff) for any options that were renamed or removed. Verify the node engine constraint change (>=22.0.0 now supported) aligns with your CI matrix.

Comment thread package.json
"typescript": "^5.3.0",
"vite": "^5.4.21",
"vitest": "^1.0.0"
"vitest": "^3.2.6"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Loose semver range allows future breaking upgrades without review

The specifier ^3.2.6 allows automatic upgrades to any 3.x release. Given that vitest has historically introduced subtle breaking changes within minor versions (e.g., snapshot format changes, reporter API changes), a loose caret range means future pnpm install or lockfile refreshes could silently pull in a breaking minor. The lockfile pins the exact version today, but any lockfile refresh will pick up the latest 3.x.

Suggested fix:

Consider pinning to an exact version (`"vitest": "3.2.6"`) or a tighter range (`"vitest": "~3.2.6"`) for a dev-only test framework where you want explicit control over upgrades. Alternatively, keep `^3.2.6` but ensure CI runs `pnpm install --frozen-lockfile` to prevent unintended upgrades.

@meroreviewer

meroreviewer Bot commented Jun 8, 2026

Copy link
Copy Markdown

Documentation Review

The following documentation may need updates based on the changes in this PR:

  • 🟡 docs/: Static HTML docs in docs/ may need updating — architecture-impacting changes detected. On merge, update-docs will scan this directory and open a PR if any pages need to change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants