chore(deps-dev): bump @vitest/ui from 4.1.9 to 4.1.10#897
chore(deps-dev): bump @vitest/ui from 4.1.9 to 4.1.10#897dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@vitest/ui](https://github.com/vitest-dev/vitest/tree/HEAD/packages/ui) from 4.1.9 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/ui) --- updated-dependencies: - dependency-name: "@vitest/ui" 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: 50474e733d
ℹ️ 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".
| specifier: ^4.1.9 | ||
| version: 4.1.9(vitest@4.1.9) | ||
| specifier: ^4.1.10 | ||
| version: 4.1.10(vitest@4.1.9) |
There was a problem hiding this comment.
The lockfile now installs @vitest/ui@4.1.10 against vitest@4.1.9, but the added package metadata declares an exact vitest: 4.1.10 peer. In installs that enforce peers, or when running vitest --ui, this pairs the UI with unsupported Vitest internals; bump vitest and @vitest/coverage-v8 in the same update, or keep the UI on 4.1.9.
Useful? React with 👍 / 👎.
| vitest: | ||
| specifier: ^4.1.7 | ||
| version: 4.1.7(@types/node@26.1.0)(@vitest/coverage-v8@4.1.9(vitest@4.1.9))(@vitest/ui@4.1.9(vitest@4.1.9))(happy-dom@20.10.6)(vite@8.1.3(@types/node@26.1.0)(jiti@2.7.0)(yaml@2.9.0)) | ||
| version: 4.1.7(@types/node@26.1.0)(@vitest/coverage-v8@4.1.9(vitest@4.1.9))(@vitest/ui@4.1.10(vitest@4.1.9))(happy-dom@20.10.6)(vite@8.1.3(@types/node@26.1.0)(jiti@2.7.0)(yaml@2.9.0)) |
There was a problem hiding this comment.
This changed importer is for packages/blue-sdk-wagmi, one of the frozen deprecated packages, and it now resolves its Vitest graph through @vitest/ui@4.1.10. Since this PR is only a Dependabot dev-dependency bump, not deprecation metadata or source deletion, updating the dependency graph for that frozen package violates the repo's freeze; keep the frozen importers unchanged or exclude them from the lockfile update.
AGENTS.md reference: AGENTS.md:L82-L83
Useful? React with 👍 / 👎.
| vitest: | ||
| specifier: ^4.1.7 | ||
| version: 4.1.7(@types/node@26.1.0)(@vitest/coverage-v8@4.1.9(vitest@4.1.9))(@vitest/ui@4.1.9(vitest@4.1.9))(happy-dom@20.10.6)(vite@8.1.3(@types/node@26.1.0)(jiti@2.7.0)(yaml@2.9.0)) | ||
| version: 4.1.7(@types/node@26.1.0)(@vitest/coverage-v8@4.1.9(vitest@4.1.9))(@vitest/ui@4.1.10(vitest@4.1.9))(happy-dom@20.10.6)(vite@8.1.3(@types/node@26.1.0)(jiti@2.7.0)(yaml@2.9.0)) |
There was a problem hiding this comment.
This changed importer is for packages/blue-sdk-wagmi, one of the frozen deprecated packages, and it now resolves its Vitest graph through @vitest/ui@4.1.10. Since this PR is only a Dependabot dev-dependency bump, not deprecation metadata or source deletion, updating the dependency graph for that frozen package violates the repo's freeze; keep the frozen importers unchanged or exclude them from the lockfile update.
Useful? React with 👍 / 👎.
Bumps @vitest/ui from 4.1.9 to 4.1.10.
Release notes
Sourced from @vitest/ui's releases.
Commits
db616d2chore: release v4.1.10 (#10718)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)