Bump @vitest/mocker and vitest - #39
Conversation
Bumps [@vitest/mocker](https://github.com/vitest-dev/vitest/tree/HEAD/packages/mocker) to 4.1.11 and updates ancestor dependency [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). These dependencies need to be updated together. Updates `@vitest/mocker` from 4.1.5 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/mocker) Updates `vitest` from 4.1.5 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/mocker" dependency-version: 4.1.11 dependency-type: indirect - dependency-name: vitest dependency-version: 4.1.11 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Claude Code Review
Claude Code Review is paused for this repository. To reconnect it, an admin of this repository's GitHub organization (or the account owner, for personal repositories) who can also manage your Claude organization's Code Review settings needs to re-link GitHub in Code Review settings. This is a one-time step.
Tip: disable this comment in your organization's Code Review settings.
There was a problem hiding this comment.
🟡 Changes recommended
The Vitest bump brings in toolchain dependencies with a stricter Node engine requirement than the repo currently declares, which can cause install/runtime issues for supported Node versions.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
This PR updates the repo’s test runner tooling by bumping vitest (and its coupled transitive @vitest/mocker) to 4.1.11, refreshing the lockfile accordingly.
Changes:
- Bump
vitestfrom^4.1.5to^4.1.11inpackage.json. - Regenerate
package-lock.jsonto reflect the updated Vitest/Vite toolchain and related transitive dependency updates.
File summaries
| File | Description |
|---|---|
| package.json | Updates the Vitest dev dependency version. |
| package-lock.json | Updates locked versions for Vitest, @vitest/*, Vite, and other transitive deps. |
Review details
- Files reviewed: 1/2 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| "devDependencies": { | ||
| "vitest": "^4.1.5" | ||
| "vitest": "^4.1.11" | ||
| }, |
Bumps @vitest/mocker to 4.1.11 and updates ancestor dependency vitest. These dependencies need to be updated together.
Updates
@vitest/mockerfrom 4.1.5 to 4.1.11Release notes
Sourced from @vitest/mocker's releases.
... (truncated)
Commits
9bd8d46chore: release v4.1.11 (#10995)fe5a11dfix(mocker): restrict redirect mocks to the fs allowlist [backport to v4] (#1...db616d2chore: release v4.1.10 (#10718)a7a61e7chore: release v4.1.9 (#10598)2c9559cfix(mocker): hoist vi.mock() for vite-plus/test imports [backport to v4] (#10...e61f2ddchore: release v4.1.8a09d472chore: release v4.1.7a8fd24cchore: release v4.1.6Updates
vitestfrom 4.1.5 to 4.1.11Release 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.