chore(deps): bump @cloudflare/workers-types from v4 to v5

[rh-hemartin]

Summary

• Bump @cloudflare/workers-types from ^4.20250420.0 to ^5.20260708.1
• Resolves peer dependency conflict with wrangler@4.110.0 from chore(deps): update dependency @cloudflare/vitest-pool-workers to v0.18.4 #3453
• Typecheck passes clean (0 errors)

Test plan

• npm update completes without errors
• npm run check (svelte-check) passes with 0 errors

🤖 Generated with Claude Code

[qodo-code-review]

PR Summary by Qodo

chore(deps): bump @cloudflare/workers-types to v5

⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Bump @cloudflare/workers-types to the v5 release line.
• Align devDependencies with wrangler@4.x peer dependency requirements.
• Unblock installs/typecheck by resolving the workers-types peer conflict.

High-Level Assessment

The approach (updating the dependency to satisfy wrangler's peer requirement) is the standard and lowest-risk fix. Alternatives like pinning/downgrading wrangler or forcing peer resolution would add ongoing maintenance and are not warranted for a straightforward type package bump.

Files changed (1) +1 / -1

Other (1) +1 / -1

package.jsonBump @cloudflare/workers-types to ^5.20260708.1 +1/-1

Bump @cloudflare/workers-types to ^5.20260708.1

• Updates the devDependency version range for @cloudflare/workers-types from the v4 line to the v5 line. This resolves the peer dependency conflict introduced by newer wrangler versions.

package.json

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 10:37 AM UTC · Completed 10:43 AM UTC
Commit: 6992c18 · View workflow run →

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

[github-actions]

Site preview

Preview: https://57ea05b5-site.fullsend-ai.workers.dev

Commit: 6992c18236a001332b4854bcdf7b5b71faa514c1

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[fullsend-ai-review]

Looks good to me

[ralphbean]

I added it to the merge queue b/c its so simple. I hope that's ok, @rh-hemartin .

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 3:20 PM UTC · Completed 3:28 PM UTC
Commit: 6992c18 · View workflow run →

[fullsend-ai-retro]

PR #4002 was a straightforward dependency version bump (@cloudflare/workers-types v4→v5) — 1 line changed in package.json plus lockfile regeneration. The review agent correctly approved in ~6 minutes with no findings, the human agreed ~4.5 hours later, and the PR was merged cleanly. No rework iterations.

Review quality: Correct outcome — the agent identified this as a low-risk mechanical change and approved. No issues were missed.

Token cost concern: The review agent dispatched 4 sub-agents (visible as 4 Agent tool calls in the workflow log) for this 1-line version bump. The pr-review skill's own scope constraint table (section 3e) correctly classifies version bumps as "mechanical/value-only" with trivial scope (≤5 tool calls per sub-agent), but the dispatch examples table (section 3c) lacks a row for dependency bumps, and the dispatch logic doesn't suppress conditional sub-agents when the scope classification is trivial. The comparable "Typo fix in README" example dispatches only 2 sub-agents.

Retro value: This retro itself is running on a simple dependency PR with no agent workflow issues. Multiple existing open issues already propose skipping retro for this class of PR: #3833, #3847, #3951, #4006, #3780. One proposal below addresses the review dispatch efficiency; the retro-skip is already well-covered by existing issues.

Proposals filed

• pr-review skill: reduce sub-agent dispatch for mechanical/value-only changes like dependency bumps (in fullsend-ai/fullsend)