Skip to content

chore(deps-dev): bump vitest from 4.1.10 to 4.1.11 #813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dependabot wants to merge 1 commit into
base: develop
Choose a base branch
from
+2 −2
Open

chore(deps-dev): bump vitest from 4.1.10 to 4.1.11 #813

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -347,7 +347,7 @@
"typescript": "~7.0.2",
"vite": "8.2.1",
"vite-plugin-mkcert": "2.1.0",
"vitest": "4.1.10",
"vitest": "4.1.11",

@chatgpt-codex-connector chatgpt-codex-connector Bot Sep 9, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Regenerate the checked-in Bun lockfile

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 👍 / 👎.

"wait-port": "1.1.0"
},
"engines": {
Expand Down
2 changes: 1 addition & 1 deletion packages/agent/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,6 @@
"@vitest/ui": "4.1.10",
"bun-types": "latest",
"typescript": "~7.0.2",
"vitest": "4.1.10"
"vitest": "4.1.11"

@chatgpt-codex-connector chatgpt-codex-connector Bot Sep 9, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Upgrade the Vitest companion packages together

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 👍 / 👎.

}
}
Loading