chore(deps-dev): bump vitest from 4.1.10 to 4.1.11 in /packages/agent - #814
chore(deps-dev): bump vitest from 4.1.10 to 4.1.11 in /packages/agent#814dependabot[bot] wants to merge 1 commit into
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
4 Skipped Deployments
|
![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: 4c1300ff77
ℹ️ 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".
| "bun-types": "latest", | ||
| "typescript": "~7.0.2", | ||
| "vitest": "4.1.10" | ||
| "vitest": "4.1.11" |
There was a problem hiding this comment.
Every clean CI installation uses bun install --frozen-lockfile in .github/actions/setup-js/action.yml:24-26, and the agent image does the same in packages/agent/Dockerfile:23-24, but this commit leaves the agent workspace entry in bun.lock pinned to vitest 4.1.10 while requesting the exact version 4.1.11 here. Since Bun documents this flag as “Disallow changes to lockfile,” these installs cannot reconcile the manifest and will stop before tests or the image build run; regenerate and commit bun.lock with this dependency update.
AGENTS.md reference: AGENTS.md:L313-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.
Even after regenerating the lockfile, the normal agent test path in packages/agent/scripts/run-tests.mjs:21-22 delegates to node-cli.js, whose resolver checks the repository-root binary before the package-local binary (scripts/dev/node-cli.js:73-80); the root manifest still pins that binary to Vitest 4.1.10. Coverage also hardcodes the root binary in packages/agent/scripts/run-coverage.mjs:8-14, so this package-only bump does not apply 4.1.11's fixes to the ordinary test, watch, UI, or coverage commands. Upgrade the root Vitest toolchain in lockstep or change these commands to resolve the agent-local binary.
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.