Repository navigation
build(deps-dev): bump vitest from 4.1.11 to 5.0.4 - #147
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.11 to 5.0.4. - [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/v5.0.4/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 5.0.4 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Codex review: needs maintainer review before merge. What this changesThis PR upgrades four workspace packages to Vitest 5.0.4 and disables filesystem module caching for Worker tests. Example: Run the API suite with Vitest 5.0.4 and Cloudflare's test plugin 1.4.0.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness✅ Ready for maintainer review Keep this PR open: main still uses Vitest 4, and the current head addresses the earlier Worker test failure without changing assertions or setup; no actionable defects remain. Priority: P3 Before mergeNone. FindingsNone. Agent review detailsHow this fits togetherVitest executes SDK, CLI, and API tests; the API configuration connects it through Cloudflare's plugin to local workerd and D1, producing results for the CI test gate. flowchart LR
A[SDK and CLI tests] --> B[Vitest 5]
C[API tests] --> B
B --> D[Cloudflare test plugin]
D --> E[Local workerd and D1]
B --> F[CI results]
E --> F
Technical reviewBest possible solution: Retain the focused Vitest upgrade and API cache setting with the existing Worker test setup. Do we have a high-confidence way to reproduce the issue? This dependency update reports no current-main product bug; GitHub confirms the earlier PR head failed Run Test and the reviewed head passes it. Is this the best way to solve the issue? Disabling the existing cache option only for workerd addresses the host-filesystem boundary directly while preserving the supported plugin pairing and existing tests. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against 5ebf8ebc3905. Provenance checked
TestingProof path: in-process harness. SecurityNone. EvidenceWhat I checked:
Likely related people:
LabelsLabel changes:
Label justifications:
Rating scale6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior. WorkflowClawSweeper edits this one comment on every review. Comment HistoryReview history (1 earlier review cycle)
Reviewed October 15, 2026, 10:57 AM ET / 14:57 UTC (Revision 2). |
|
@clawsweeper re-review Please review current head No release operation is authorized. |
|
🦞👀 Re-review progress:
|
vincentkoc
left a comment
There was a problem hiding this comment.
Reviewed head 889b212f3f36d6a6dfa39a8f1c9c7a290a5256f1. The API-only fsModuleCache setting preserves the existing Cloudflare inline module transport and leaves setup, isolation, assertions, and timeouts intact. Full independent source review has no actionable findings; exact-head hosted CI passes, including all 15 API test files in https://github.com/openclaw/krillswitch/actions/runs/38747845526/job/116466085912. Current-head ClawSweeper review is clear. No production behavior or data-model change is introduced.
Bumps vitest from 4.1.11 to 5.0.4.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
6a11cf6chore: release v5.0.4 (#11554)58c86edchore(deps): update all non-major dependencies (#11550)0fa80f5fix(coverage): filenames containing brackets incorrectly showing as uncovered...bf04b9cfix(browser): run browser instances as workers (#11525)3e3624crefactor: resolve maxWorkers once in config (#11524)26642f7fix: respect root in projects (#11521)c06012afeat(experimental): add an option to cache dependencies instead of statically...4ef000afix(coverage):allowExternalfails to include uncovered files (#11513)1da6640feat: supporttest.ui.themeoption (#11499)b618afdfix(vm): bindthistomodule.exports(#11504)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)