Repository navigation
fix(commons-gateway): pin vitest to 4.x for vitest-pool-workers compatibility - #77
Conversation
…tibility #69 bumped vitest to ^5.0.3, but @cloudflare/vitest-pool-workers (0.22.0, and 0.23.0, the latest) declares peer vitest ^4.1.0. npm ci cannot resolve that, so every Workers Builds run on a branch carrying #69 failed at the install step (npm 10.9.2 reports it as "Cannot read properties of null (reading 'edgesOut')"). main never ran the check: the non-production trigger excludes main, so the breakage went unseen. Restore vitest ^4.1.9 and its lockfile from before #69. With that fixed, npm 10.9.2 surfaced a second peer conflict: wrangler 4.124.0 wants @cloudflare/workers-types ^5.20260815.1 (peerOptional) while we pinned ^4. Move workers-types to ^5.20261025.1. Tell Dependabot to ignore vitest >=5 here until pool-workers accepts it. Verified with node 24 + npm 10.9.2 (Cloudflare's build image): npm ci ok, vitest 12/12, tsc --noEmit ok, wrangler deploy --dry-run ok.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Dependency versions and update policy .github/dependabot.yml, workers/commons-gateway/package.json |
The package manifest upgrades @cloudflare/workers-types to ^5.20261025.1 and changes Vitest to ^4.1.9. Dependabot ignores Vitest versions >=5.0.0. |
Priority:
Estimated code review effort: 2 (Simple) | ~5 minutes
Change: Bug fix
Merge Risk: 
Minimal · up to 4053a
-
No actionable merge-blocking risk was identified.
Pre-merge checks: 
4 · 
1
-
Failed checks: 1 warning Passed checks: 4 passed-
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)
-
Full details: Description check
-
Explanation
The description explains the root cause, changes, verification results, and post-merge actions. However, it omits most required template sections, including Scope, Truth status, Prior art and reuse, the required Tests checklist and result, Docs and registries, and Risk.
Resolution
Update the description to use the repository template. Add the missing sections and complete the required checkboxes, test result, truth-status evidence, scope, reuse decision, documentation impact, blast radius, and rollback plan.
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
floss | 4053aff | Commit Preview URL Branch Preview URL |
Oct 25 2026, 02:48 AM |
Root cause
#69 (c6a1f8b, merged 2026-10-01) raised
vitestto^5.0.3inworkers/commons-gateway.@cloudflare/vitest-pool-workers(0.22.0, and 0.23.0, the latest) declares peervitest ^4.1.0, sonpm cicannot resolve the tree.Evidence: Workers Builds
67c454cb…(#43) and053a4309…(#73) both fail at Installing project dependencies: npm clean-install withnpm error Cannot read properties of null (reading 'edgesOut'), which is how npm 10.9.2 reports this peer conflict. npm 11 on the same tree printsERESOLVE … peer vitest@"^4.1.0" from @cloudflare/vitest-pool-workers@0.22.0.npm cifails the same way onmain, #43, and #73.Why main looked green: the "Deploy non-production branches" trigger excludes
main, so main never runs this check. #41 passed only because its branch predates #69.Change
vitest ^4.1.9and the commons-gateway lockfile from before chore(deps): bump vitest from 4.1.9 to 5.0.3 in /workers/commons-gateway #69.@cloudflare/workers-typesfrom^4to^5.20261025.1. Once the vitest conflict is gone, npm 10.9.2 reports a second one: wrangler 4.124.0 declares an optional peer ofworkers-types ^5.20260815.1..github/dependabot.yml: ignorevitest >=5for/workers/commons-gatewayuntil pool-workers accepts it. The rest of the config is unchanged.Verification (node 24 + npm 10.9.2, matching the Cloudflare build image)
npm ci: okvitest run: 12/12tsc --noEmit: okwrangler deploy --dry-run: okAfter merge
#43 and #73 (and any branch with #69) need updating from
mainto get Workers Builds green again.Summary by CodeRabbit