build(deps-dev): bump vitest from 3.2.7 to 4.1.11 - #1340
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.2.7 to 4.1.11. - [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/v4.1.11/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.11 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit c99bdad. Configure here.
| "typescript": "^5.0.4", | ||
| "vite": "^6.4.3", | ||
| "vitest": "3.2.7" | ||
| "vitest": "4.1.11" |
There was a problem hiding this comment.
Coverage package version mismatch
High Severity
vitest is now 4.1.11 while @vitest/coverage-v8 remains 3.2.7. yarn test always runs with --coverage, and Vitest requires the coverage provider to match its own version, so unit and e2e coverage runs can fail or report incorrectly.
Reviewed by Cursor Bugbot for commit c99bdad. Configure here.
| "typescript": "^5.0.4", | ||
| "vite": "^6.4.3", | ||
| "vitest": "3.2.7" | ||
| "vitest": "4.1.11" |
There was a problem hiding this comment.
Vitest 4 drops Node 18
Medium Severity
vitest 4.x dropped Node 18, but this repo still pins Node 18.20.6 via Volta, declares engines.node as >=18.20.6, and runs the unit-test CI matrix on Node 18. Those local and CI test jobs can fail after this upgrade.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit c99bdad. Configure here.
Bumps vitest from 3.2.7 to 4.1.11.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
9bd8d46chore: release v4.1.11 (#10995)9851dbcfix(browser): trigger playwright/chromium gc on lower disk availability [back...db616d2chore: release v4.1.10 (#10718)bae52b5fix(vm): fix external module resolve error with deps optimizer query for enco...a7a61e7chore: release v4.1.9 (#10598)934b0f5fix(pool): prevent test run hang on worker crash (#10543) [backport to v4] (#...7fb2965fix(browser): wait for orchestrator readiness before resolving browser sessio...a518019fix: fiximportOriginalwith optimizer and query import [backport to v4] (#...e61f2ddchore: release v4.1.8e4067b3fix(browser): disable clientcdpAPI whenallowWrite/allowExec: false[ba...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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.