[workers-devprod]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@cloudflare/config@0.25.0

Minor Changes

• #16175 d8b1fca Thanks @jamesopstad! - Allow Worker bindings to be included conditionally

  Binding entries set to false, null, or undefined are now omitted from env. Generated environment types make conditionally included bindings optional.

  export default defineConfig(({ mode }) => ({
    worker: {
      name: "my-worker",
      compatibilityDate: "2026-10-09",
      env: {
        PRODUCTION_KV:
          mode === "production" && bindings.kv({ id: "production-kv-id" }),
        STAGING_API_ORIGIN:
          mode === "staging"
            ? bindings.text("https://staging.example.com")
            : undefined,
      },
    },
  }));

create-cloudflare@2.74.0

Minor Changes

• #16129 070c3f2 Thanks @james-elicx! - Support projects configured with cloudflare.config.ts and the cf CLI

  Framework generators can now scaffold projects that use cloudflare.config.ts and the cf CLI in place of a Wrangler configuration file. C3 detects these projects and installs cf instead of Wrangler, logs in and selects accounts with cf, and looks up the deployed Worker's URL with cf. Projects that use Wrangler are unaffected.

Patch Changes

• #16129 070c3f2 Thanks @james-elicx! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  create-vinext-app	1.0.0-beta.3	1.0.0

• #16205 7e702ed Thanks @dependabot! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  create-qwik	1.20.1	1.20.2

• #16206 92676ad Thanks @dependabot! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  create-vike	0.0.681	0.0.682

• #16207 478a6b5 Thanks @dependabot! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  sv	1.0.1	1.1.1

• #16208 0693fbc Thanks @dependabot! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  create-astro	5.2.4	5.2.6

• #16209 f508d50 Thanks @dependabot! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  create-next-app	16.3.8	16.4.0

• #16210 c09832d Thanks @dependabot! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  nuxi	3.37.0	4.0.1

• #16211 7ba4e38 Thanks @dependabot! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  @angular/create	22.2.1	22.2.2

• #15288 1787b35 Thanks @AiAlchemist0! - Skip mkdir when the project parent directory already exists, so create-cloudflare works at a Windows drive root (E:\) instead of throwing EPERM.

• #16210 c09832d Thanks @dependabot! - Check Node.js compatibility when creating Nuxt projects and select a supported version

  Before launching nuxi 4, both Nuxt templates check its supported Node.js versions: 22.21.0 or later in the 22.x release line, 24.11.0 or later in the 24.x release line, or 26.0.0 or later. Unsupported versions receive an error showing the required range, the current version, and guidance to upgrade Node.js.

  Generated Nuxt projects now pin Node.js 22.23.1 in their own .node-version file, replacing the outdated Node.js 18 pin that was written to the parent directory.

@cloudflare/workers-auth@0.14.0

Minor Changes

• #16184 6c4153e Thanks @mtlemilio! - Allow cf consumers to explicitly request the hyperdrive-planetscale:setup OAuth scope

  The scope remains excluded from default logins so permission to create Cloudflare-billed PlanetScale databases is requested only by commands that need it.

• #16038 dc3e4df Thanks @dario-piotrowicz! - Use consumer-specific CLI names and commands in shared user-facing messages

  Shared deployment, container, configuration, and authentication helpers can now render commands and configuration filenames for their calling CLI while preserving Wrangler-compatible defaults. This prevents cf workflows from presenting Wrangler-branded guidance when an equivalent cf command exists.

Patch Changes

• #16151 cafd3f9 Thanks @DevVettel! - Time out the OAuth token request instead of waiting indefinitely

  The request that exchanges an authorization code or refresh token for an access token had no timeout, so a stalled connection (for example behind an HTTP proxy) could leave wrangler login hanging silently for many minutes after the browser step had succeeded. The request now gives up after 30 seconds and reports that the Cloudflare auth server could not be reached.

• Updated dependencies [dc3e4df]:

  • @cloudflare/workers-utils@0.47.2

wrangler@4.150.0

Minor Changes

• #16231 091e5ec Thanks @WalshyDev! - Upload source maps by default for wrangler deploy, wrangler versions upload and wrangler preview

  When upload_source_maps isn't set in config or via --upload-source-maps, Wrangler now generates and uploads source maps so stack traces in logs and wrangler tail point at your original source without extra setup. In this default mode, source maps that can't be resolved (for example inline data: maps or missing .map files from a custom build) are skipped rather than failing the upload. Setting upload_source_maps = true keeps the existing strict behaviour, and upload_source_maps = false (or --no-upload-source-maps for deploy and versions upload) opts out.

  wrangler build --experimental-cf-build-output is unchanged and still only includes source maps when upload_source_maps = true.

• #16128 daae435 Thanks @redsteadz! - Stop wrangler deploy, wrangler versions upload and wrangler preview in projects that build for the Cloudflare CLI (cf)

  If your project builds through cf, deploying it with Wrangler reads a different configuration, so it could update the wrong Worker or fail without explaining why. These commands now stop before uploading anything, name the .cloudflare/output directory they found, and tell you to run cf deploy instead. If that directory is just left over from an earlier build, deleting it restores the Wrangler workflow.

  Ordinary Wrangler projects are unaffected, and --dry-run still works on deploy and versions upload. This is a new guard for the experimental Build Output Specification rather than a fix, and it gives three stable commands a failure mode they did not have before, so it is a minor.

Patch Changes

• #16161 fcf625d Thanks @dario-piotrowicz! - Clarify the Worker not found error during CI deploy validation

  Wrangler now reports that the configured Worker could not be found in the account instead of incorrectly describing the failure as a name mismatch.

• #16156 18f061c Thanks @armancharan! - Ignore .wrangler writes in the dev assets watcher

  wrangler dev reloaded in a loop when assets.directory was the project root, because the assets watcher treated wrangler's own writes under .wrangler as asset changes and dropped in-flight requests. The watcher now ignores the project's .wrangler directory and dev.persist, except when that path is the assets directory.

• #16025 61e07fd Thanks @kohjunhao! - Fix optional Docker lookups printing Docker CLI errors during successful builds

  cf build looks for Container images left behind by earlier builds so it can remove them. This lookup is best effort, but when Docker could not be reached it still printed errors such as Cannot connect to the Docker daemon, even when the build succeeded and no image needed Docker. Docker commands whose output Wrangler reads no longer forward the Docker CLI's error output to the terminal. If one of these commands fails in a way that stops the command, the error message still includes the Docker CLI's output.

• #16151 cafd3f9 Thanks @DevVettel! - Time out the OAuth token request instead of waiting indefinitely

  The request that exchanges an authorization code or refresh token for an access token had no timeout, so a stalled connection (for example behind an HTTP proxy) could leave wrangler login hanging silently for many minutes after the browser step had succeeded. The request now gives up after 30 seconds and reports that the Cloudflare auth server could not be reached.

• #15517 ea64ec4 Thanks @xgame92! - Preserve binding options when provisioning resources through a redirected config

  Wrangler now writes provisioned resource identifiers to both the redirected and original config files without copying other binding options between them. This prevents generated relative paths such as D1 migrations_dir from replacing user-authored paths during Vite deployments.

• #16219 d232454 Thanks @petebacondarwin! - Honor X-Forwarded-Proto for incoming development requests behind TLS-terminating proxies

  Miniflare now uses the original client protocol when constructing URLs for network requests. This also prevents Wrangler from downgrading HTTPS URLs in response headers such as Location and WWW-Authenticate when a tunnel forwards requests over HTTP. Explicit programmatic request URLs and configured upstream origins remain authoritative.

• Updated dependencies [5152bf8, 9f87de8, 9be5ec7, d232454]:

  • miniflare@5.20261006.2-beta

@cloudflare/autoconfig@0.7.8

Patch Changes

• Updated dependencies [dc3e4df, d8b1fca]:
  • @cloudflare/workers-utils@0.47.2
  • @cloudflare/config@0.25.0
  • @cloudflare/cli-shared-helpers@0.2.6

@cloudflare/build-output-utils@0.9.1

Patch Changes

• Updated dependencies [d8b1fca]:
  • @cloudflare/config@0.25.0

@cloudflare/cli-shared-helpers@0.2.6

Patch Changes

• Updated dependencies [dc3e4df]:
  • @cloudflare/workers-utils@0.47.2

@cloudflare/containers-shared@0.21.6

Patch Changes

• #16025 61e07fd Thanks @kohjunhao! - Fix optional Docker lookups printing Docker CLI errors during successful builds

  cf build looks for Container images left behind by earlier builds so it can remove them. This lookup is best effort, but when Docker could not be reached it still printed errors such as Cannot connect to the Docker daemon, even when the build succeeded and no image needed Docker. Docker commands whose output Wrangler reads no longer forward the Docker CLI's error output to the terminal. If one of these commands fails in a way that stops the command, the error message still includes the Docker CLI's output.

• #16038 dc3e4df Thanks @dario-piotrowicz! - Use consumer-specific CLI names and commands in shared user-facing messages

  Shared deployment, container, configuration, and authentication helpers can now render commands and configuration filenames for their calling CLI while preserving Wrangler-compatible defaults. This prevents cf workflows from presenting Wrangler-branded guidance when an equivalent cf command exists.

• Updated dependencies [dc3e4df, d8b1fca]:

  • @cloudflare/workers-utils@0.47.2
  • @cloudflare/config@0.25.0
  • @cloudflare/build-output-utils@0.9.1
  • @cloudflare/cli-shared-helpers@0.2.6

@cloudflare/deploy-helpers@0.20.2

Patch Changes

• #16161 fcf625d Thanks @dario-piotrowicz! - Clarify the Worker not found error during CI deploy validation

  Wrangler now reports that the configured Worker could not be found in the account instead of incorrectly describing the failure as a name mismatch.

• #16038 dc3e4df Thanks @dario-piotrowicz! - Use consumer-specific CLI names and commands in shared user-facing messages

  Shared deployment, container, configuration, and authentication helpers can now render commands and configuration filenames for their calling CLI while preserving Wrangler-compatible defaults. This prevents cf workflows from presenting Wrangler-branded guidance when an equivalent cf command exists.

• #15517 ea64ec4 Thanks @xgame92! - Preserve binding options when provisioning resources through a redirected config

  Wrangler now writes provisioned resource identifiers to both the redirected and original config files without copying other binding options between them. This prevents generated relative paths such as D1 migrations_dir from replacing user-authored paths during Vite deployments.

• Updated dependencies [5152bf8, 9f87de8, 9be5ec7, 61e07fd, dc3e4df, d8b1fca, d232454]:

  • miniflare@5.20261006.2-beta
  • @cloudflare/containers-shared@0.21.6
  • @cloudflare/workers-utils@0.47.2
  • @cloudflare/config@0.25.0
  • @cloudflare/cli-shared-helpers@0.2.6

miniflare@5.20261006.2-beta

Patch Changes

• #16224 5152bf8 Thanks @adrianhall! - Fix short-lived local sessions hanging instead of exiting after dispose()

  A Miniflare instance using shared local storage could keep the Node process alive after dispose() resolved, because a filesystem watcher on the dev registry directory was left running. A one-shot local command would do its work and print its result, then never exit — cf d1 migrations apply --local, for example, applied every migration successfully and still had to be killed. Disposal now releases the watcher reliably, so the process exits on its own.

• #16146 9f87de8 Thanks @armancharan! - Replay the request body when dispatchFetch() retries HTTP 421

  A known-length POST that receives 421 used to throw UND_ERR_REQ_CONTENT_LENGTH_MISMATCH. The retry aborted the connection before the response was finished, which dropped the body while keeping the original Content-Length. The abort from that retry is now ignored so the same bytes are sent again.

• #16221 9be5ec7 Thanks @jamesopstad! - Promote Miniflare v5 prereleases from alpha to beta.

  This aligns the Miniflare prereleases with cf and @cloudflare/vite-plugin.

• #16219 d232454 Thanks @petebacondarwin! - Honor X-Forwarded-Proto for incoming development requests behind TLS-terminating proxies

  Miniflare now uses the original client protocol when constructing URLs for network requests. This also prevents Wrangler from downgrading HTTPS URLs in response headers such as Location and WWW-Authenticate when a tunnel forwards requests over HTTP. Explicit programmatic request URLs and configured upstream origins remain authoritative.

@cloudflare/pages-shared@0.13.196

Patch Changes

• Updated dependencies [5152bf8, 9f87de8, 9be5ec7, d232454]:
  • miniflare@5.20261006.2-beta

@cloudflare/runtime-types@0.1.10

Patch Changes

• Updated dependencies [5152bf8, 9f87de8, 9be5ec7, d232454]:
  • miniflare@5.20261006.2-beta

@cloudflare/vite-plugin@1.63.2

Patch Changes

• #16025 61e07fd Thanks @kohjunhao! - Fix optional Docker lookups printing Docker CLI errors during successful builds

  cf build looks for Container images left behind by earlier builds so it can remove them. This lookup is best effort, but when Docker could not be reached it still printed errors such as Cannot connect to the Docker daemon, even when the build succeeded and no image needed Docker. Docker commands whose output Wrangler reads no longer forward the Docker CLI's error output to the terminal. If one of these commands fails in a way that stops the command, the error message still includes the Docker CLI's output.

• #16038 dc3e4df Thanks @dario-piotrowicz! - Use consumer-specific CLI names and commands in shared user-facing messages

  Shared deployment, container, configuration, and authentication helpers can now render commands and configuration filenames for their calling CLI while preserving Wrangler-compatible defaults. This prevents cf workflows from presenting Wrangler-branded guidance when an equivalent cf command exists.

• Updated dependencies [fcf625d, 091e5ec, 5152bf8, 9f87de8, daae435, 18f061c, 9be5ec7, 61e07fd, cafd3f9, ea64ec4, d232454]:

  • wrangler@4.150.0
  • miniflare@5.20261006.2-beta

@cloudflare/vitest-plugin@1.4.1

Patch Changes

• Updated dependencies [fcf625d, 091e5ec, 5152bf8, 9f87de8, daae435, 18f061c, 9be5ec7, 61e07fd, cafd3f9, ea64ec4, d232454]:
  • wrangler@4.150.0
  • miniflare@5.20261006.2-beta

@cloudflare/workers-utils@0.47.2

Patch Changes

• #16038 dc3e4df Thanks @dario-piotrowicz! - Use consumer-specific CLI names and commands in shared user-facing messages

  Shared deployment, container, configuration, and authentication helpers can now render commands and configuration filenames for their calling CLI while preserving Wrangler-compatible defaults. This prevents cf workflows from presenting Wrangler-branded guidance when an equivalent cf command exists.

@cloudflare/remote-bindings@0.0.46

Patch Changes

• Updated dependencies [6c4153e, fcf625d, 5152bf8, 9f87de8, 9be5ec7, dc3e4df, cafd3f9, ea64ec4, d232454]:
  • @cloudflare/workers-auth@0.14.0
  • @cloudflare/deploy-helpers@0.20.2
  • miniflare@5.20261006.2-beta
  • @cloudflare/workers-utils@0.47.2
  • @cloudflare/cli-shared-helpers@0.2.6

[devin-ai-integration]

Note

Newer findings are available below. Devin Review posted a newer report on this PR, in addition to the findings presented here.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[pkg-pr-new]

@cloudflare/autoconfig

npm i https://pkg.pr.new/@cloudflare/autoconfig@16162

@cloudflare/build-output-utils

npm i https://pkg.pr.new/@cloudflare/build-output-utils@16162

@cloudflare/codemods

npm i https://pkg.pr.new/@cloudflare/codemods@16162

@cloudflare/config

npm i https://pkg.pr.new/@cloudflare/config@16162

@cloudflare/containers-shared

npm i https://pkg.pr.new/@cloudflare/containers-shared@16162

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@16162

@cloudflare/deploy-helpers

npm i https://pkg.pr.new/@cloudflare/deploy-helpers@16162

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@16162

miniflare

npm i https://pkg.pr.new/miniflare@16162

@cloudflare/pages-functions

npm i https://pkg.pr.new/@cloudflare/pages-functions@16162

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@16162

@cloudflare/runtime-types

npm i https://pkg.pr.new/@cloudflare/runtime-types@16162

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@16162

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@16162

@cloudflare/vitest-plugin

npm i https://pkg.pr.new/@cloudflare/vitest-plugin@16162

@cloudflare/workers-auth

npm i https://pkg.pr.new/@cloudflare/workers-auth@16162

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@16162

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@16162

wrangler

npm i https://pkg.pr.new/wrangler@16162

commit: bf62cfc