Patch Changes

• Updated dependencies [34c71ce, f7c82a4, 7ddd865, 6479fc5, e5ae13a]:
  • miniflare@4.20250523.0

Patch Changes

• #9268 7344344 Thanks @gabivlj! - wrangler containers delete handles API errors correctly

Patch Changes

• #9262 2c3d8dd Thanks @workers-devprod! - fix: add no-op props to ctx in getPlatformProxy to fix type mismatch

• #8681 7a57c14 Thanks @workers-devprod! - fix(miniflare): strip CF-Connecting-IP header from all outbound requests

• #9128 c535845 Thanks @dario-piotrowicz! - fix: remove outdated js-doc comment for unstable_startDevWorker's entrypoint

• #9259 b742171 Thanks @workers-devprod! - Relax R2 bucket validation for pages dev commands

• #9172 4e943b1 Thanks @vicb! - validate r2 bucket names

• #9250 b2b5ee8 Thanks @workers-devprod! - fix: strip CF-Connecting-IP header within fetch

  In v4.15.0, Miniflare began stripping the CF-Connecting-IP header via a global outbound service, which led to a TCP connection regression due to a bug in Workerd. This PR patches the fetch API to strip the header during local wrangler dev sessions as a temporary workaround until the underlying issue is resolved.

• #9267 8b4f24a Thanks @workers-devprod! - fix: setting triggers.crons:[] in Wrangler config should delete deployed cron schedules

• #9163 d67cd0d Thanks @petebacondarwin! - Do not report "d1 execute" command file missing error to Sentry

• #8957 9d4ff5b Thanks @workers-devprod! - Make sure custom build logging output is more clearly signposted, and make sure it doesn't interfere with the interactive dev session output.

• #9166 9b4c91d Thanks @lambrospetrou! - Fix d1 info command showing read_replication: [object Object]

• Updated dependencies [7a57c14, b2b5ee8, 56a0d6e]:

  • miniflare@3.20250408.2

Patch Changes

• #8681 7a57c14 Thanks @workers-devprod! - fix(miniflare): strip CF-Connecting-IP header from all outbound requests

• #9250 b2b5ee8 Thanks @workers-devprod! - fix: strip CF-Connecting-IP header within fetch

  In v4.15.0, Miniflare began stripping the CF-Connecting-IP header via a global outbound service, which led to a TCP connection regression due to a bug in Workerd. This PR patches the fetch API to strip the header during local wrangler dev sessions as a temporary workaround until the underlying issue is resolved.

• #9211 56a0d6e Thanks @petebacondarwin! - fix: ensure the fetch proxy message port is started

  While Node.js will start the message port automatically when a message event listener is added,
  this diverges from the standard Web API for message ports, which require you to explicitly start
  listening on the port.

Patch Changes

• Updated dependencies [7344344]:
  • wrangler@4.16.1

Patch Changes

• #9322 1bae861 Thanks @justinvdm! - Fix regex to correctly detect additional module imports with __ in path

• Updated dependencies [7344344]:

  • wrangler@4.16.1

Minor Changes

• #9288 3b8f7f1 Thanks @petebacondarwin! - allow --name and --env args on wrangler deploy

  Previously it was not possible to provide a Worker name as a command line argument at the same time as setting the Wrangler environment.
  Now specifying --name is supported and will override any names set in the Wrangler config:

  wrangler.json

  {
  	"name": "config-worker"
  	"env": {
  		"staging": { "name": "config-worker-env" }
  	}
  }

  Command	Previous (Worker name)	Proposed (Worker name)	Comment
  wrangler deploy --name=args-worker	"args-worker"	"args-worker"	CLI arg used
  wrangler deploy --name=args-worker --env=staging	Error	"args-worker"	CLI arg used
  wrangler deploy --name=args-worker --env=prod	Error	"args-worker"	CLI arg used
  wrangler deploy	"config-worker"	"config-worker"	Top-level config used
  wrangler deploy --env=staging	"config-worker-env"	"config-worker-env"	Named env config used
  wrangler deploy --env=prod	"config-worker-prod"	"config-worker-prod"	CLI arg and top-level config combined

• #9265 16de0d5 Thanks @edmundhung! - docs: add documentation links to individual config properties in the JSON schema of the Wrangler config file

Patch Changes

• #9234 2fe6219 Thanks @emily-shen! - fix: add no-op props to ctx in getPlatformProxy to fix type mismatch

• #9269 66d975e Thanks @dario-piotrowicz! - Wire up mixed-mode remote bindings for multi-worker wrangler dev

  Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a multi-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

  Also include the ai binding since the bindings is already remote by default anyways.

• #9151 5ab035d Thanks @gabivlj! - wrangler containers can be configured with the kind of application rollout on apply

• #9231 02d40ed Thanks @dario-piotrowicz! - Wire up mixed-mode remote bindings for (single-worker) wrangler dev

  Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a single-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

  Also include the ai binding since the bindings is already remote by default anyways.

• #9221 2ef31a9 Thanks @vicb! - bump @cloudflare/unenv-preset

• #9277 db5ea8f Thanks @penalosa! - Support Mixed Mode for more binding types

• #9266 f2a16f1 Thanks @petebacondarwin! - fix: setting triggers.crons:[] in Wrangler config should delete deployed cron schedules

• #9245 b87b472 Thanks @penalosa! - Support Mixed Mode Dispatch Namespaces

• Updated dependencies [db5ea8f, b87b472]:

  • miniflare@4.20250508.3

Patch Changes

• #9277 db5ea8f Thanks @penalosa! - Support Mixed Mode for more binding types

• #9245 b87b472 Thanks @penalosa! - Support Mixed Mode Dispatch Namespaces

Patch Changes

• #9291 40040de Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  nuxi	3.25.0	3.25.1

• #9292 14c7d04 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  @angular/create	19.2.11	19.2.12

• #9293 fa4dd47 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  sv	0.8.3	0.8.6

• #9294 625aeca Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  create-hono	0.18.0	0.19.1

• #9274 14dc393 Thanks @vicb! - fix the env interface name in Next

Patch Changes

• #9227 ab8dab1 Thanks @petebacondarwin! - allow miniflare assets options to override wrangler assets options

• Updated dependencies [2fe6219, 66d975e, 5ab035d, 02d40ed, 2ef31a9, db5ea8f, f2a16f1, 3b8f7f1, 16de0d5, b87b472]:

  • wrangler@4.16.0
  • miniflare@4.20250508.3