chore(deps-dev): bump vitest from 4.1.7 to 4.1.10#896
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.7 to 4.1.10. - [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.10/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.10 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.
Tip: disable this comment in your organization's Code Review settings.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f03d2baa7d
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "viem": "2.54.2", | ||
| "vite": "8.1.3", | ||
| "vitest": "^4.1.9" | ||
| "vitest": "^4.1.10" |
There was a problem hiding this comment.
The root test:ci script runs Vitest with --coverage, but this bump advances only vitest; the lockfile still resolves @vitest/coverage-v8@4.1.9 and @vitest/ui@4.1.9, and their package entries declare exact vitest: 4.1.9 peers while every importer now gets vitest@4.1.10. That leaves installs and coverage/UI runs on an unsupported mixed Vitest stack, so the companion packages should be bumped to 4.1.10 in the same change.
Useful? React with 👍 / 👎.
| "typescript": "^6.0.3", | ||
| "viem": "^2.50.4", | ||
| "vitest": "^4.1.7", | ||
| "vitest": "^4.1.10", |
There was a problem hiding this comment.
This dependency bump also updates the manifest for a frozen/deprecated package, and the same Vitest change appears in bundler-sdk-viem, migration-sdk-viem, simulation-sdk, and simulation-sdk-wagmi. Because this PR is a test dependency refresh rather than deprecation metadata or source deletion, these package manifests should be excluded from the bump to avoid reviving maintenance on frozen surfaces.
AGENTS.md reference: packages/blue-sdk-wagmi/AGENTS.md:L5-L6
Useful? React with 👍 / 👎.
| "typescript": "^6.0.3", | ||
| "viem": "^2.50.4", | ||
| "vitest": "^4.1.7", | ||
| "vitest": "^4.1.10", |
There was a problem hiding this comment.
This dependency bump also updates the manifest for a frozen/deprecated package, and the same Vitest change appears in bundler-sdk-viem, migration-sdk-viem, simulation-sdk, and simulation-sdk-wagmi. Because this PR is a test dependency refresh rather than deprecation metadata or source deletion, these package manifests should be excluded from the bump to avoid reviving maintenance on frozen surfaces.
Useful? React with 👍 / 👎.
Bumps vitest from 4.1.7 to 4.1.10.
Release notes
Sourced from vitest's releases.
Commits
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)