Skip to content

fix(config): unblock inbound-worker deploy by aligning wrangler with workers-types v5 - #118

Merged
alekslinde merged 1 commit into
mainfrom
fix/worker-deploy-wrangler-types-peer
Aug 2, 2026
Merged

fix(config): unblock inbound-worker deploy by aligning wrangler with workers-types v5#118
alekslinde merged 1 commit into
mainfrom
fix/worker-deploy-wrangler-types-peer

Conversation

@alekslinde

@alekslinde alekslinde commented Aug 2, 2026

Copy link
Copy Markdown
Owner

The "Deploy inbound email worker" job failed at npm ci with an ERESOLVE
peer conflict: @cloudflare/workers-types was bumped to v5 (#95) but wrangler
was left at ^4.103.0, whose peerOptional pins workers-types to ^4. npm's
strict peer resolution rejected the v4/v5 mismatch, so the install — and thus
the whole deploy — failed before it began.

Verified locally: npm ci, npm test (6/6), and tsc --noEmit all pass in
workers/inbound-email.

…dencies

The "Deploy inbound email worker" job's wrangler-action steps still passed
wranglerVersion "3", while the worker is now built and typed against wrangler
4 (^4.115.0) and @cloudflare/workers-types v5. Deploying with wrangler 3 a
worker developed on wrangler 4 is a version drift that risks config/runtime
mismatches. Align both steps to "4".

The earlier npm ci ERESOLVE failure (workers-types v5 vs wrangler 4.103's v4
peer) is already resolved on main by the #110 wrangler ^4.115.0 bump, so this
change is workflow-only.

Verified in workers/inbound-email against current deps: npm ci, npm test
(6/6), tsc --noEmit, and `wrangler deploy --dry-run` (4.115.0) all pass.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TboCmBUmkhg7nTnXfSVDxi
@alekslinde
alekslinde force-pushed the fix/worker-deploy-wrangler-types-peer branch from 449a9c0 to 081f51d Compare August 2, 2026 22:41
@alekslinde
alekslinde merged commit fcfd793 into main Aug 2, 2026
1 check passed
@alekslinde
alekslinde deleted the fix/worker-deploy-wrangler-types-peer branch August 2, 2026 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants