chore(deps-dev): bump vitest from 4.1.10 to 4.1.11 - #813
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.10 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
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5076b567c0
ℹ️ 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".
| "vite": "8.2.1", | ||
| "vite-plugin-mkcert": "2.1.0", | ||
| "vitest": "4.1.10", | ||
| "vitest": "4.1.11", |
There was a problem hiding this comment.
The edited exact requirement is still recorded as vitest: 4.1.10 in both relevant bun.lock workspace entries, and the resolved package is also 4.1.10. Every affected GitHub workflow installs through .github/actions/setup-js/action.yml with bun install --frozen-lockfile; bun install --help defines that flag as “Disallow changes to lockfile,” so a clean CI checkout cannot reconcile these manifests and stops during dependency setup. Regenerate and commit bun.lock with the dependency update.
AGENTS.md reference: AGENTS.md:L316-L318
Useful? React with 👍 / 👎.
| "bun-types": "latest", | ||
| "typescript": "~7.0.2", | ||
| "vitest": "4.1.10" | ||
| "vitest": "4.1.11" |
There was a problem hiding this comment.
This changes the agent's Vitest runner to 4.1.11 while leaving @vitest/coverage-v8 and @vitest/ui at 4.1.10; their package metadata declares an exact vitest: 4.1.10 peer dependency. The Agent workflow always runs bun run test:coverage, so after the lockfile is regenerated it will install an unsupported mixed Vitest graph on that required path. Align the coverage/UI packages—and the root coverage provider—with Vitest 4.1.11.
Useful? React with 👍 / 👎.
Bumps vitest from 4.1.10 to 4.1.11.
Release notes
Sourced from vitest's releases.
Commits
9bd8d46chore: release v4.1.11 (#10995)9851dbcfix(browser): trigger playwright/chromium gc on lower disk availability [back...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.