Minor Changes

• #10939 d4b4c90 Thanks @danielrs! - Config preview_urls defaults to workers_dev value.

  Originally, we were defaulting config.preview_urls to true, but we
  were accidentally enabling Preview URLs for users that only had
  config.workers_dev=false.

  Then, we set the default value of config.preview_urls to false, but we
  were accidentally disabling Preview URLs for users that only had
  config.workers_dev=true.

  Rather than defaulting config.preview_urls to true or false, we
  default to the resolved value of config.workers_dev. Should result in a
  clearer user experience.

• #11027 1a2bbf8 Thanks @jamesopstad! - Statically replace the value of process.env.NODE_ENV with development for development builds and production for production builds if it is not set. Else, use the given value. This ensures that libraries, such as React, that branch code based on process.env.NODE_ENV can be properly tree shaken.

• #9705 0ee1a68 Thanks @hiendv! - Add params type to Workflow type generation. E.g.

  interface Env {
  	MY_WORKFLOW: Workflow<
  		Parameters<import("./src/index").MyWorkflow["run"]>[0]["payload"]
  	>;
  }

• #10867 dd5f769 Thanks @austin-mc! - Add media binding support

Patch Changes

• #11018 5124818 Thanks @dario-piotrowicz! - Improve potential errors thrown by startRemoteProxySession by including more information

• #11019 6643bd4 Thanks @dario-piotrowicz! - Fix observability.logs.persist being flagged as an unexpected field during the wrangler config file validation

• #10768 8211bc9 Thanks @dario-piotrowicz! - Update logs handling to use the new handleStructuredLogs miniflare option

• #10997 3bb034f Thanks @nikitassharma! - When either WRANGLER_OUTPUT_FILE_PATH or WRANGLER_OUTPUT_FILE_DIRECTORY are set
  in the environment, then command failures will append a line to the output file
  encoding the error code and message, if present.

• #10986 43503c7 Thanks @emily-shen! - fix: cleanup any running containers again on wrangler dev exit

• #11000 a6de9db Thanks @jonboulle! - always load container image into local store during build

  BuildKit supports different build drivers. When using the more modern docker-container driver (which is now the default on some systems, e.g. a standard Docker installation on Fedora Linux), it will not automatically load the built image into the local image store. Since wrangler expects the image to be there (e.g. when calling getImageRepoTags), it will thus fail, e.g.:

  ⎔ Preparing container image(s)...
  [+] Building 0.3s (8/8) FINISHED                                                                                                                                                                                                     docker-container:default
  
  [...]
  
  WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
  
  ✘ [ERROR] failed inspecting image locally: Error response from daemon: failed to find image cloudflare-dev/sandbox:f86e40e4: docker.io/cloudflare-dev/sandbox:f86e40e4: No such image
  
  

  Explicitly setting the --load flag (equivalent to -o type=docker) during the build fixes this and should make the build a bit more portable without requiring users to change their default build driver configuration.

• #10994 d39c8b5 Thanks @pombosilva! - Make Workflows instances list command cursor based

• #10892 7d0417b Thanks @dario-piotrowicz! - improve the diffing representation for wrangler deploy (run under --x-remote-diff-check)

• Updated dependencies [36d7054, dd5f769, ee7d710, 8211bc9]:

  • miniflare@4.20251011.0
  • @cloudflare/unenv-preset@2.7.8

Minor Changes

• #10867 dd5f769 Thanks @austin-mc! - Add media binding support

• #10768 8211bc9 Thanks @dario-piotrowicz! - Add handleStructuredLogs option that allows consumers of the workerd structured logs to print such logs without additional boilerplate

Patch Changes

• #10963 36d7054 Thanks @dependabot! - chore: update dependencies of "miniflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20251008.0	1.20251011.0

Minor Changes

• #10989 da37501 Thanks @dom96! - Fixes generation of 'name' in Python uv.lock template

• #10943 9d843fe Thanks @valfz! - fixed creating index.js with wrong extension when Vue project is created with JavaScript

• #10990 c07036b Thanks @dom96! - Python templates' package.json scripts now use pywrangler

Patch Changes

• #10948 04c5dc7 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  create-qwik	1.16.1	1.17.0

• #10949 44dc255 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  @angular/create	20.3.4	20.3.6

• #10950 39dbb39 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  sv	0.9.7	0.9.8

• #10951 46c31e1 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  nuxi	3.28.0	3.29.3

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

  The following dependency versions have been updated:

  Dependency	From	To
  create-react-router	7.9.3	7.9.4

• #10914 890a606 Thanks @devin-ai-integration! - Fix git commit failures when global pre-commit hooks are configured. When initializing projects, create-cloudflare now uses git commit --no-verify to bypass any globally configured git hooks that might fail and block project initialization.

Patch Changes

• Updated dependencies [5124818, d4b4c90, 6643bd4, 1a2bbf8, 36d7054, 0ee1a68, 8211bc9, 3bb034f, 43503c7, dd5f769, a6de9db, d39c8b5, 7d0417b, 8211bc9]:
  • wrangler@4.44.0
  • miniflare@4.20251011.0

Patch Changes

• #10707 092c999 Thanks @edmundhung! - Add request cancellation support

  Workers running on Vite can now listen to the abort event with request.signal to perform tasks when the request is canceled by the client. For more information, see the Request documentation.

• #10768 8211bc9 Thanks @dario-piotrowicz! - Ensure that logs are printed at the correct log level

  The changes here ensure that logs generated by Workers are printed accordingly to the logLevel the user defines (either in their Vite config file or via the --logLevel CLI flag)

• #10899 e2809b5 Thanks @edmundhung! - fix: track server restart in module scope

  When using @cloudflare/vite-plugin with React Router, miniflare might be disposed during restart. This change makes sure to track when the dev server restart in module scope to avoid unexpected behavior.

• Updated dependencies [5124818, d4b4c90, 6643bd4, 1a2bbf8, 36d7054, 0ee1a68, 8211bc9, 3bb034f, 43503c7, dd5f769, a6de9db, ee7d710, d39c8b5, 7d0417b, 8211bc9]:

  • wrangler@4.44.0
  • miniflare@4.20251011.0
  • @cloudflare/unenv-preset@2.7.8

Patch Changes

• #10954 ee7d710 Thanks @vicb! - Use the native node:cluster module when available.

  It is enabled when the enable_nodejs_cluster_module compatibility flag is set.

Patch Changes

• Updated dependencies [36d7054, dd5f769, 8211bc9]:
  • miniflare@4.20251011.0

Patch Changes

• #11007 cf16deb Thanks @gpanders! - Correctly handle image names that contain a slash

• #11000 a6de9db Thanks @jonboulle! - always load container image into local store during build

  BuildKit supports different build drivers. When using the more modern docker-container driver (which is now the default on some systems, e.g. a standard Docker installation on Fedora Linux), it will not automatically load the built image into the local image store. Since wrangler expects the image to be there (e.g. when calling getImageRepoTags), it will thus fail, e.g.:

  ⎔ Preparing container image(s)...
  [+] Building 0.3s (8/8) FINISHED                                                                                                                                                                                                     docker-container:default
  
  [...]
  
  WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
  
  ✘ [ERROR] failed inspecting image locally: Error response from daemon: failed to find image cloudflare-dev/sandbox:f86e40e4: docker.io/cloudflare-dev/sandbox:f86e40e4: No such image
  
  

  Explicitly setting the --load flag (equivalent to -o type=docker) during the build fixes this and should make the build a bit more portable without requiring users to change their default build driver configuration.

Minor Changes

• #10911 940b44d Thanks @devin-ai-integration! - feat: wrangler init --from-dash now generates wrangler.jsonc config files instead of wrangler.toml files

Patch Changes

• #10938 e52d0ec Thanks @penalosa! - Acquire Cloudflare Access tokens for additional requests made during a wrangler dev --remote session

• #10923 2429533 Thanks @emily-shen! - fix: update docker manifest inspect to use full image registry uri when checking if the image exists remotely

• #10521 88b5b7f Thanks @penalosa! - Improves the Wrangler auto-provisioning feature (gated behind the experimental flag --x-provision) by:

  • Writing back changes to the user's config file (not necessary, but can make it resilient to binding name changes)
  • Fixing --dry-run, which previously threw an error when your config file had auto provisioned resources
  • Improve R2 bindings display to include the bucket_name from the config file on upload
  • Fixing bindings view for specific versions to not display TOML

Patch Changes

• Updated dependencies [e52d0ec, 940b44d, 2429533, 88b5b7f]:
  • wrangler@4.43.0