NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #4709 most downloaded on npm
Command-line interface for all things Cloudflare Workers
Latest stable
4.166.0
Last release 2 days ago
20 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
14 years old
4980 releases · first in 2012
Drag across the ruler to compare, or tap a release to open it.
This patch includes six upstream security fixes covering caching, redirects, and Subresource Integrity verification. Update the shared Undici dependen…
#16961 bf7568a Thanks @dario-piotrowicz! - Show configured trigger targets during experimental wrangler triggers deploy --dry-run
Dry runs now print a "Would deploy" summary of routes, custom domains, cron schedules, Queue producers and consumers, Workflows, event triggers, and Email Routing addresses instead of exiting without a summary. Explicitly empty cron schedules and Email Routing addresses are shown as removals. The preview makes no API requests or authentication checks; when workers.dev is enabled, it reports that setting without looking up the account's subdomain.
#16679 be6aa81 Thanks @mglewis! - Add images.url_transformations to the Wrangler configuration
The images block now accepts a url_transformations object for controlling /cdn-cgi/image/ transformations on requests served by a Worker. enabled is required, and allowed_origins optionally lists the origins images may be fetched from (use ["*"] to allow any origin). binding is now optional, so url_transformations can be configured without an Images binding:
Like the rest of the images block, url_transformations is not inherited by named environments, and must be specified in each environment that needs it.
cloudflare.config.ts gains the equivalent setting as a top-level images field on the Worker, with the Images binding remaining in env:
export default defineConfig({
worker: {
name: "my-worker",
compatibilityDate: "2026-11-01",
images: {
urlTransformations: {
enabled: true,
allowedOrigins: ["images.example.com"],
},
},
},
});cf migrate carries images.url_transformations over to this field.
This change adds configuration and validation only. url_transformations is not supported in previews.
#14114 dce615c Thanks @dario-piotrowicz! - Add --show-diff flag to wrangler triggers deploy
When --show-diff is passed, the command fetches the currently deployed trigger configuration from the remote worker and displays a colored diff against the local configuration before deploying. This covers routes, custom domains, cron schedules, and the workers_dev/preview_urls subdomain settings. Route and custom-domain lists are fetched only when that category has local entries to deploy, avoiding unnecessary permission requirements. Queue consumers and event triggers are not compared.
The flag also works with --dry-run to preview these changes without actually deploying. Displaying a diff requires authentication, including during a dry run.
#17031 95fd4c2 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-19
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#17031 95fd4c2 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261118.1 | ^5.20261119.1 |
| workerd | 1.20261118.1 | 1.20261119.1 |
#16961 bf7568a Thanks @dario-piotrowicz! - Validate external Workflow settings before updating Worker triggers
Reject limits, concurrency, schedules, default_retention, and jurisdiction configured on external Workflows before making trigger API calls. This prevents failed deployments from partially updating workers.dev or routes; dry runs reject the same invalid configurations.
#17044 56974d4 Thanks @petebacondarwin! - Warn when invocation logs are enabled while logs are disabled
Configuration validation now warns when observability.logs.invocation_logs is true and observability.logs.enabled is false. Invocation logging remains disabled until observability.logs.enabled is set to true.
#17072 3c91a13 Thanks @mykcs! - Recover when concurrent wrangler preview builds try to create the same Preview name.
If another build creates a Preview after the initial lookup, Wrangler now reads the existing Preview and applies the requested Preview settings instead of failing with Cloudflare API error 100338. Other creation errors still fail, and existing Previews are never deleted.
#17081 08eeaf4 Thanks @Naapperas! - Wait for a just-uploaded Worker version to become readable during deploys
For a few seconds after a version is uploaded, the Workers API can alternate between returning it and reporting it as not found. wrangler versions deploy failed on the first not-found read, and wrangler deploy for Durable Object-managed containers gave up after about 2 seconds and reported that the container settings were not fully applied.
Both now keep retrying a not-found version for up to about 12 seconds and log a message while they wait. These reads also retry transient API failures, such as server errors, rate limiting, timeouts and network errors, which can wait longer when the API asks for it. Other errors still fail immediately.
#17030 f3f7bbc Thanks @cpojer! - Stop running Docker at the end of builds for projects with no Containers
Builds that write the Build Output Specification ran docker image ls on every build to find image tags left by a previous build, even when the project configured no Containers. On a machine with Docker installed this added about a quarter of a second to each build, and the build waited on the Docker CLI for as long as it took to respond. The lookup is now skipped when the project has no Containers and the build output being replaced had none either. Projects that configure Containers, and the first build after the last Container is removed, still remove previous tags as before.
#17043 4f5b118 Thanks @petebacondarwin! - Update Undici to 7.30.2 to include upstream security fixes
This patch includes six upstream security fixes covering caching, redirects, and Subresource Integrity verification. Update the shared Undici dependency and matching types together so affected packages ship the patched version.
#17035 1b563db Thanks @petebacondarwin! - Fix remote bindings authentication with API tokens scoped to an individual Worker
Remote bindings now create preview sessions through the Worker-scoped endpoint. When the response includes a usable exchange URL, its hostname is used without account-wide Workers subdomain access; otherwise, the existing account subdomain lookup or registration is used. This applies to getPlatformProxy and remote bindings in Wrangler, the Cloudflare Vite plugin, and the Vitest integration. Tokens still need permission to update the named Worker.
Updated dependencies [8712fc5, 95fd4c2, 95fd4c2, be6aa81, 8f45554, 56974d4, 08eeaf4, 629f135, 4f5b118, 629f135, 8f45554]:
Your coding agent can read these notes before it upgrades. Set up the MCP server →
wrangler d1 migrations apply <db> --remote --force
#10598 24bd3c3 Thanks @Ehbraheem! - Add a new --force flag to d1 migrations apply which skips the interactive confirmation and applies any pending migrations non-interactively. This is useful for CI and automation.
Usage example:
wrangler d1 migrations apply <db> --remote --force
Fixes #5017
#16019 8f26e90 Thanks @penalosa! - Correct the dry-run setup message to say "exiting now" instead of "existing now".
The previous wording contained a typo and appeared in Wrangler setup output and other consumers of shared autoconfig.
#17003 3595295 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-18
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#17003 3595295 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261117.1 | ^5.20261118.1 |
| workerd | 1.20261117.1 | 1.20261118.1 |
#16719 f833c8a Thanks @jaeminbird! - Report .dev.vars and .env files that are not UTF-8 instead of silently loading no variables
Before Wrangler would incorrectly read non UTF-8 .dev.vars and .env files as UTF-8. A .dev.vars file that is not UTF-8 now stops wrangler dev with a message that says how to fix it, and a .env file that is not UTF-8 is skipped with a warning. UTF-8 files, with or without a BOM, load as before.
#14334 67d7c0a Thanks @Divkix! - Replace the unmaintained asset hashing dependency with hash-wasm
Keep asset hashes unchanged for Workers and Pages deployments and local Pages development while using a maintained WebAssembly implementation.
#16949 110c162 Thanks @edmundhung! - Fail remote RPC binding requests on network errors instead of hanging
Remote bindings that connect over RPC treated every network failure, such as being offline, a DNS or TLS error, as a preview reload. The request then waited silently for a reload that never came. These requests now fail with the error, while GET and HEAD requests interrupted by an actual reload are still retried.
#14578 6750663 Thanks @penalosa! - Fix TypeScript errors when importing Wrangler's APIs
Projects that import Wrangler's APIs, such as getPlatformProxy or defineWranglerConfig, can now type-check with skipLibCheck: false. The published types no longer refer to missing internal packages, and their required type dependencies are installed automatically.
Updated dependencies [0a4315f, 3595295, 3595295, 6750663, 6750663, d04e667, 6750663, 5a6e450]:
Workers VPC (open beta) service create and update commands accept --certificate-authority and --client-certificate UUIDs. Use either flag alone or bot
#16450 5f05841 Thanks @xortive! - Add custom CA and client certificate references to Workers VPC service TLS settings
Workers VPC (open beta) service create and update commands accept --certificate-authority and --client-certificate UUIDs. Use either flag alone or both together. Whenever you supply either reference, explicitly choose --cert-verification-mode:
verify_full: verify the origin certificate chain and hostname (the platform default).verify_ca: verify the chain but skip hostname verification, weakening origin identity checks.disabled: do not verify the origin certificate; this allows connections to impersonated origins and is unsafe for production.For HTTP services, these settings apply to HTTPS connections, not plaintext HTTP. TCP services can use them for upstream TLS, including PostgreSQL.
TLS settings are per-service only: host and resolver networks have no TLS settings or inheritance. Omitting TLS settings uses platform defaults (certificate chain and hostname verification). Explicit mode-only configuration, including verify_full, is accepted. A custom CA cannot be combined with disabled; a client certificate without a custom CA can.
Upload certificates using the existing commands, then use the returned IDs below. Replace <ca-uuid>, <client-uuid>, <tunnel-uuid>, and service IDs with your own values; certificate references must be valid UUIDs. Upload replacement certificates the same way before rotating their references.
pnpm exec wrangler cert upload certificate-authority --ca-cert ./ca.pem --name private-ca
pnpm exec wrangler cert upload mtls-certificate --cert ./client.pem --key ./client-key.pem --name private-clientCreate an HTTPS service with both a custom trust chain and an mTLS client certificate, or a PostgreSQL TCP service with only a custom CA:
pnpm exec wrangler vpc service create private-web \
--type http --https-port 443 --ipv4 10.0.0.10 --tunnel-id <tunnel-uuid> \
--certificate-authority <ca-uuid> --client-certificate <client-uuid> \
--cert-verification-mode verify_full
pnpm exec wrangler vpc service create private-db \
--type tcp --tcp-port 5432 --app-protocol postgresql \
--hostname db.internal.example --resolver-ips 10.0.0.53 --tunnel-id <tunnel-uuid> \
--certificate-authority <ca-uuid> --cert-verification-mode verify_fullFor client-certificate-only configuration, use --client-certificate <client-uuid> --cert-verification-mode verify_full instead of the certificate flags in either create command.
Updates replace the complete service configuration, including TLS settings, in a single request, the same as cf workers-vpc services update. Pass every TLS option the service should keep: certificate references and the verification mode that you omit are cleared, and an update without TLS options returns the service to the platform defaults. Removing a reference releases its backend certificate binding but does not delete the uploaded account certificate. For example, rotate the web service's client certificate while keeping its CA:
pnpm exec wrangler vpc service update <web-service-uuid> \
--name private-web --type http --https-port 443 \
--ipv4 10.0.0.10 --tunnel-id <tunnel-uuid> \
--certificate-authority <ca-uuid> --client-certificate <replacement-client-uuid> \
--cert-verification-mode verify_fullTo remove the CA while keeping the client certificate, repeat the update with only --client-certificate <client-uuid> and a verification mode.
Inspect the service's verification mode and CA/client certificate UUIDs (or None), without exposing certificate or private-key contents:
pnpm exec wrangler vpc service get <service-uuid>#16974 77b5ca7 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-17
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16974 77b5ca7 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261116.1 | ^5.20261117.1 |
| workerd | 1.20261116.1 | 1.20261117.1 |
vite build and the experimental wrangler build --experimental-cf-build-output now write Build Output v1, with account settings nested under settings i
#16917 d36b39d Thanks @jamesopstad! - Write Build Output to .cloudflare/output/v1/ and record the producer
vite build and the experimental wrangler build --experimental-cf-build-output now write Build Output v1, with account settings nested under settings in the root config.json. They also record themselves as the producer, so readers can name the tool that wrote the output in error messages. Previews from Build Output read the account settings from their new location.
#16246 349fc4e Thanks @leostera! - Start local Workflows from Artifacts events
Declare Artifacts events on exports.workflow({ name, events }) in cloudflare.config.ts to start the owning Workflow locally in cf, Vite, and Workers Vitest. Wrangler configurations continue to use triggers.events. Native config conversion derives those targets from the Workflow export, and cf migrate attaches existing event subscriptions to their matching Workflow exports.
Local Artifacts namespaces publish the documented cf.artifacts.* messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions.
#16803 b219078 Thanks @petebacondarwin! - Run experimental cf projects with their installed Vite or Vite+ commands
cf dev, cf build, and deployments that build your project can use Vite or Vite+ even when no framework command is detected. This removes the need for the internal cf-vite delegate and supports dependencies declared and hoisted at the root of a configured workspace. A workspace application using a custom-named Vite config should declare @cloudflare/vite-plugin in its own manifest, or add vite or vite-plus as a dependency or dev dependency to identify its tooling; this keeps shared root tools from selecting Vite for non-Vite siblings. Configs passed later via --config are evaluated by Vite when the command runs. Existing framework commands keep their priority. Consumers resolve bare executables using the detected nodeModulesPaths in order, adding .bin to each directory. Lookup stops at the validated workspace root; standalone applications use only their own node_modules/.bin.
Project inspection can recognize an existing Cloudflare configuration before dependencies are installed. Running a command provides guidance when the required tools are missing or the plugin version does not support cf profiles (>=2.0.0-beta.v.13 <3). Vite evaluates the project configuration when the command runs, including dynamic configs and custom config files. Repair guidance uses the project’s detected package manager. Automatic setup asks users to convert CommonJS .cjs and .cts Vite configs to ESM imports and exports in .mjs or .mts before adding the ESM-only Cloudflare plugin. Native builds also work with the Windows shell. Pages migration safeguards, unsupported-framework setup checks, and Wrangler command selection retain their existing behavior.
#16944 db3c071 Thanks @danlapid! - Stop wrangler dev from missing config file changes made soon after a reload
wrangler dev replaced its config file watcher on every reload without waiting for the new one to start, so a change saved in that gap was never applied. It now keeps one watcher while the set of watched files is unchanged, and reports a config as applied only once its files are being watched. A second change saved within 50 ms of the previous one is no longer dropped either.
#16920 81e56dd Thanks @benbuzbee! - Use the effective max_instances value when choosing the default container rollout steps
When max_instances was omitted, Wrangler deployed 20 instances but chose rollout steps as if there were 0 instances, so the rollout used a single 100% step. Wrangler now uses [10, 100] for omitted max_instances, while still using a single 100% step when max_instances is 0 or 1.
#16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16946 e97c9f8 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261113.1 | ^5.20261116.1 |
| workerd | 1.20261113.1 | 1.20261116.1 |
#16874 4335eac Thanks @petebacondarwin! - Avoid redundant OAuth refreshes after a sibling process updates credentials
Check access-token expiry and select the refresh token from the same fresh credential snapshot. When a sibling has already saved a valid access token, reuse it without another exchange or write. This prevents an unnecessary rotation that can let an older response overwrite a newer refresh token.
#16917 d36b39d Thanks @jamesopstad! - Detect Cloudflare Build Output of any version before deploying
wrangler deploy, wrangler versions upload and wrangler preview refuse to run in a project that has Cloudflare Build Output, because that output belongs to cf. Detection now looks for any .cloudflare/output/v<N>/ directory rather than only the root config of the current version, so output left by an older or newer cf is still caught.
Behavior change: Artifacts bindings now default to the local simulator during development, like KV, R2 and D1. Previously, an omitted remote in Wrangl
#16735 f005593 Thanks @leostera! - Use the local simulator for Artifacts bindings that omit remote
Behavior change: Artifacts bindings now default to the local simulator during development, like KV, R2 and D1. Previously, an omitted remote in Wrangler and the Vite plugin used the deployed Artifacts resource. If you want deployed repos in wrangler dev or vite dev, set "remote": true on the binding (dev: { remote: true } in cloudflare.config.ts). Artifacts is in beta, so this ships as a minor release.
While remote is omitted, wrangler dev, getPlatformProxy() and the Vite plugin warn when remote bindings are enabled, once for each binding rather than on every config reload: "Artifacts binding REPOS uses the local simulator by default. Set remote: true to use deployed repos, or remote: false to silence this warning." Workers Vitest and wrangler dev --local already used the simulator, so they don't warn. Local Artifacts needs no Cloudflare credentials, but requires Git 2.32 or newer on the host.
#16749 032f8c2 Thanks @vaishnav-mk! - Reject settings on a workflows binding to a Workflow declared in exports
A workflows binding can still bind a Workflow that the Worker declares in exports, but it can no longer set limits, concurrency, schedules, default_retention, or jurisdiction for it. Set them on the export instead. Previously the binding and the export could both set them as long as they agreed, so configurations that set them on the binding now stop with an error that says which setting to move.
#16749 032f8c2 Thanks @vaishnav-mk! - Upload Workflow export settings with the Worker
wrangler deploy and wrangler versions upload now include the settings of each workflow export (limits, concurrency, schedules, default_retention, and jurisdiction) in the upload, instead of sending only its type and name. Uploads of a Worker with workflow exports also send a Cloudflare-Workers-Script-Api-Date header, which lets the Workers API provision Workflow exports from these settings as part of the upload. wrangler deploy and wrangler triggers deploy still create or update each Workflow through the Workflows API afterwards, as before.
If provisioning a scheduled Workflow fails because the account is on the free plan, wrangler deploy now explains that scheduled Workflows require a paid Workers plan.
#16849 3cea40b Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-12
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16886 63eb6da Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-13
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16849 3cea40b Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261110.1 | ^5.20261112.1 |
| workerd | 1.20261110.1 | 1.20261112.1 |
#16886 63eb6da Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261112.1 | ^5.20261113.1 |
| workerd | 1.20261112.1 | 1.20261113.1 |
#16864 3b1b408 Thanks @MattieTK! - Fix packages with nested package.json files missing from deploy metadata
Packages such as hono, stripe and @modelcontextprotocol/sdk were silently omitted from the package dependency metadata reported during wrangler deploy and wrangler versions upload. These packages are now included with their installed versions. Autoconfig and codemods also detect their installed versions correctly.
#16862 c889551 Thanks @petebacondarwin! - Fix requests hanging when a local Worker reload finishes before an inflight request fails
Wrangler now immediately processes retriable requests when the replacement Worker is already ready. Previously, these requests could remain queued until another request arrived, particularly on Windows where connection failures can take longer to report.
Updated dependencies [f005593, 61eacca, 856842e, 856842e, 3cea40b, 63eb6da, 3cea40b, 63eb6da]:
This changes the experimental Build Output that wrangler build --experimental-cf-build-output and cf-wrangler build write. Their source maps were prep
#16840 8b2a363 Thanks @jamesopstad! - Write source maps in Build Output with sources relative to each source map file
This changes the experimental Build Output that wrangler build --experimental-cf-build-output and cf-wrangler build write. Their source maps were prepared as if for upload, with sources relative to the project root. For Workers that Wrangler does not bundle, leading ../ segments were also removed, which lost the location of some files. They now point from each source map's location in bundle/ to the original files, like the source maps the Vite plugin writes.
#16833 5f539b5 Thanks @jamesopstad! - Name cf commands and cloudflare.config.ts settings in remote bindings errors from cf-wrangler
When cf runs development through the cf-wrangler delegate and remote bindings cannot be authenticated, the error now tells you to run cf auth whoami, cf auth logout and cf auth login instead of the Wrangler commands, and the Cloudflare Access hint names cf. The Flagship error for a binding whose app has not been created now names the binding's id setting instead of app_id, and suggests cf flagship apps create. wrangler dev still names Wrangler's commands and settings.
#16527 dc47e6d Thanks @petebacondarwin! - Normalize relative redirect pathnames consistently across Pages and Workers assets
Relative _redirects targets now use shared pathname normalization after placeholder replacement, keeping repeated separators within the site's path. Explicit external targets (including scheme-less URLs such as //example.com/path), query values and fragments retain their contents.
#16559 575d136 Thanks @edmundhung! - Update @netlify/build-info to 11.3.1
#16838 3626ee8 Thanks @jamesopstad! - Keep the remote bindings session when you remove the last remote binding
When you removed the last remote binding while wrangler dev was running, Wrangler restarted the remote bindings session with credentials that ignored --profile and the account_id in your Wrangler config. So it could use a different account or ask you to choose one. Wrangler now keeps the existing session, and starts a new one with your current credentials when you add a remote binding again.
Updated dependencies [dc47e6d]:
Updated dependencies [ 877b249 , 69e650c ]:
cf dev can now forward options such as --inspector-port 9229 , --ip , --var , and --persist-to to the Wrangler development runtime. The delegate reuse
#16760 cb9534f Thanks @petebacondarwin! - Support forwarded Wrangler development server options in the experimental cf-wrangler delegate
cf dev can now forward options such as --inspector-port 9229, --ip, --var, and --persist-to to the Wrangler development runtime. The delegate reuses Wrangler's dev option definitions and validation while retaining project config discovery, --mode environment selection, local development, and its .cloudflare/state default. Invalid option combinations produce a single-line usage error and exit code 2 before starting the server.
Place server options that overlap cf's global options after --, for example cf dev -- --local --persist-to "custom state". Config and script overrides, whole-worker remote development, and Wrangler's global options remain unsupported.
#16739 6af492e Thanks @GregBrimble! - Add custom Cloudflare API headers through CLOUDFLARE_API_HEADERS
Set CLOUDFLARE_API_HEADERS to a JSON object such as {"X-Custom-Header":"value"} to add headers to Cloudflare API requests. Custom headers override existing unprotected request headers, body and transport headers are protected, and header values outside the diagnostic allowlist remain redacted regardless of log sanitization settings.
#16810 cdc970b Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-10
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16810 cdc970b Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261109.1 | ^5.20261110.1 |
| workerd | 1.20261109.1 | 1.20261110.1 |
#16709 022ee9d Thanks @petebacondarwin! - Keep local Container images available for upload retries
Keep prebuilt local image tags available until the caller finishes uploading the Worker and deploying its Container applications, so a later failure can be retried without rebuilding. When image push commands request cleanup, remove the source tag only after the push succeeds.
#16740 44b39b0 Thanks @GregBrimble! - Redact header values outside a safe diagnostic allowlist, regardless of log sanitization settings.
Apply the same filtering to request, response, and request-options diagnostics. Strip X-Auth-Key alongside Authorization when forwarding local artifact Git requests.
#16758 325dc69 Thanks @petebacondarwin! - Fix JavaScript configuration parsing for Svelte projects using object spread
Use a parser that supports object spread when updating JavaScript configuration files. This prevents configuration failures for Svelte projects using Drizzle or Better Auth and other framework configurations containing modern JavaScript syntax.
Vite autoconfiguration reports a configuration error when an object spread, computed property, or accessor after the plugins array could override the Cloudflare plugin. Place the effective plugins array after these properties before retrying autoconfiguration.
Updated dependencies [cdc970b, cdc970b, 4e7e9f1, 267dadb, 44b39b0]:
Local development and Workers Vitest tests now include security fixes for their bundled dependencies. Local browser rendering also includes security f…
#16737 a589d23 Thanks @jamesopstad! - Store experimental cf-wrangler dev state in .cloudflare/state
Persist local resource data in .cloudflare/state relative to the configuration file. Direct Wrangler usage continues to default to .wrangler/state.
#16663 fe69809 Thanks @FlorentCollin! - Add --compatibility flag to wrangler d1 export
You can now export a remote D1 database that contains virtual tables, such as FTS5 or R*Tree tables:
wrangler d1 export my-database --remote --output dump.sql --compatibility sqlite3_cli_only
It accepts d1 (the default) and sqlite3_cli_only. With sqlite3_cli_only, the dump matches the output of the sqlite3 .dump command, including virtual tables. D1 cannot import this dump. sqlite3_cli_only is only supported for remote exports.
#16599 dee7a1d Thanks @petebacondarwin! - Support CLOUDFLARE_AUTH_PROFILE for shared authentication profile selection
Cloudflare tooling can pass a selected profile to child processes through CLOUDFLARE_AUTH_PROFILE. Explicit profile arguments take precedence over the variable, followed by directory bindings and the default profile. The cf-wrangler development delegate also initializes cf authentication so it reads the selected cf credentials.
Experimental cf development delegates inherit the selected profile without additional command-line flags. Vite refreshes remote authentication when the resolved profile changes, and cf-wrangler keeps its authentication scoped to the delegate invocation.
#15615 c64fdfb Thanks @svetch! - Support jurisdiction when automatically provisioning D1 databases
Set jurisdiction on a D1 binding without a database_id to create the database in that jurisdiction during deployment. For example, {"d1_databases":[{"binding":"DB","jurisdiction":"eu"}]} creates an EU-jurisdiction database.
#16066 4112820 Thanks @petebacondarwin! - Add an explicit opt-out for main module imports in generated Worker types
Use wrangler types --include-main-module=false when the Worker entrypoint is generated build output that should not be type-checked as application source. The corresponding includeMainModule option is available in the experimental type-generation API. The option is preserved by --check and automatic regeneration. Omitting the import opts out of module-derived ctx.exports typing while preserving runtime types, environment bindings, and Durable Object namespace declarations.
New SvelteKit Workers projects created with C3 use this option so their generated declarations remain stable before and after a build. Imports needed to type Durable Object, service, and Workflow bindings are unaffected.
#16648 56459a5 Thanks @dario-piotrowicz! - Update bundled third-party dependencies with known security fixes
Local development and Workers Vitest tests now include security fixes for their bundled dependencies. Local browser rendering also includes security fixes for browser downloads, archive extraction, and proxy support.
Miniflare and Wrangler now require Node.js 22.12.0 or later, matching the supported runtime range of the new browser installer.
#16746 abf924e Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-06
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16792 de10016 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-09
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16746 abf924e Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261104.1 | ^5.20261106.1 |
| workerd | 1.20261104.1 | 1.20261106.1 |
#16792 de10016 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261106.1 | ^5.20261109.1 |
| workerd | 1.20261106.1 | 1.20261109.1 |
#16726 2fb01e7 Thanks @pratham-jain33! - Warn when cron triggers are configured alongside --dispatch-namespace
When deploying a user Worker to a dispatch namespace (Workers for Platforms), cron triggers are not supported, but Wrangler previously dropped them silently: schedules configured via triggers.crons in the Wrangler config file or the --triggers CLI flag never ran and no warning was shown. Wrangler now warns that cron triggers will be ignored when deploying with --dispatch-namespace.
#16748 dc4e093 Thanks @shbernal! - Stop wrangler email routing addresses create from claiming a verification email was sent for addresses that are already verified
Cloudflare doesn't send a verification email when the destination address is already verified on the account, such as the account owner's own email. The command now shows the verification timestamp in that case. It only mentions a verification email when the address is still pending.
#15621 cff83d0 Thanks @petebacondarwin! - Report a failed Wrangler command when the CLI child is terminated by a signal
Wrangler's executable previously translated signal termination into exit code 0, which could cause callers to report a successful deployment after the operating system stopped Wrangler. Signal exits now use the conventional nonzero shell status.
#16413 3ef2afd Thanks @ghostwriternr! - Remove Container networking sidecars and snapshot clone volumes in local development
Wrangler and the Vite plugin removed only the application containers of Container-enabled Durable Objects, found by image tag, and left behind the networking sidecars and snapshot clone volumes that workerd also creates. They now leave cleanup to Miniflare, which removes all of these when the Container configuration changes, such as after a rebuild, when local development stops, and when the process exits.
#16066 4112820 Thanks @petebacondarwin! - Preserve environment inputs when automatically regenerating Worker types
Automatic type regeneration now reuses the recorded --env and --env-file options. This keeps environment-specific bindings and secret declarations consistent with the generated header and subsequent wrangler types --check runs.
#15621 cff83d0 Thanks @petebacondarwin! - Avoid materializing unused multipart request bodies
Wrangler no longer creates a full text copy of multipart API request bodies when debug logs are disabled or sanitized. This substantially reduces peak memory use when uploading large batches of static assets while preserving request-body output when unsanitized debug logging is explicitly enabled.
#16664 9b6582c Thanks @dario-piotrowicz! - Stop getPlatformProxy() asset misses from recursively calling its own listener
Requests for assets that do not exist now return a 404 response without hanging or exhausting local development resources.
Updated dependencies [fea323a, 56459a5, abf924e, de10016, abf924e, de10016, 66bc0d6]:
Set remote: false on an Artifacts binding to opt into the Miniflare simulator and persistent local repositories during development. Omitted remote con
#16186 f1d81a2 Thanks @leostera! - Support local Artifacts across Wrangler, Vite, and Workers Vitest
Set remote: false on an Artifacts binding to opt into the Miniflare simulator and persistent local repositories during development. Omitted remote continues to use the deployed resource, with a warning that changes affect real repositories; remote: true explicitly selects it. When remote bindings are disabled (wrangler dev --local, or Vite's remoteBindings: false), Artifacts bindings use the local simulator. Workers Vitest uses the local simulator when remote is omitted, so tests do not change real repositories by accident; set remote: true to test against the deployed resource. Local development does not require Cloudflare credentials, but does require Git 2.32 or newer on the host.
In Miniflare's own options, Artifacts bindings route like every other binding: only dev.remote: true with a remote proxy connection uses the deployed resource. Wrangler and Vite resolve the deployed-by-default rule, and Workers Vitest its local default, before passing options to Miniflare.
#16700 dc35efb Thanks @cjol! - Bump bundled brace-expansion to pick up security fixes
These packages bundle brace-expansion (a dependency of minimatch), and the bundled versions were affected by published advisories. The bundles now include brace-expansion 2.1.7 (from 2.0.1) and 5.0.12 (from 5.0.5). Normal glob patterns expand as before; only the pathological patterns targeted by the advisories are handled differently.
#16700 dc35efb Thanks @cjol! - Bump bundled fast-xml-parser from 4.4.1 to 4.5.5 to pick up security fixes
Miniflare bundles fast-xml-parser into its local R2 S3 API, and Wrangler bundles it through the AWS SDK used by wrangler pipelines. Version 4.4.1 is affected by several published advisories, and 4.5.5 includes their fixes. XML handling does not change.
#16700 dc35efb Thanks @cjol! - Bump bundled minimatch from 5.1.6 to 5.1.9 to pick up security fixes
These packages bundle minimatch, and 5.1.6 is affected by published ReDoS advisories. Version 5.1.9 includes the fixes. 5.1.8 is skipped because it broke recursive ** matching, which D1's migrations_pattern relies on.
#16700 dc35efb Thanks @cjol! - Bump bundled shell-quote from 1.10.0 to 1.11.0 to pick up a security fix
shell-quote is bundled into Wrangler, which uses it to parse and quote shell commands such as custom build and Pages dev commands. Version 1.10.0 is affected by a published advisory, and 1.11.0 includes the fix. Command parsing does not change.
#16700 dc35efb Thanks @cjol! - Bump bundled yaml from 2.8.1 to 2.9.0 to pick up a security fix
yaml is bundled into Wrangler, which uses it to show container application details. Version 2.8.1 is affected by a published advisory, and versions from 2.8.3 onwards include the fix. Output does not change.
#16688 fa3edb3 Thanks @FlorentCollin! - Use the account_id from the configuration file in wrangler d1 migrations list --remote
Before this change, the command ignored the account_id in the configuration file. When your login had access to more than one account, the command failed in non-interactive mode. In interactive mode, it asked you to select an account. The command now uses the configured account_id, as wrangler d1 migrations apply does.
#16695 b2061f4 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-04
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16695 b2061f4 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261103.1 | ^5.20261104.1 |
| workerd | 1.20261103.1 | 1.20261104.1 |
#16306 36e64f2 Thanks @efalcao! - Report Cloudflare Access login redirects on remote bindings instead of looping until "Too many redirects"
When a remote bindings request reached a workers.dev host protected by Access without valid Access credentials (for example, Access was added after the dev server started, the CF_Authorization cookie expired, or Access was not detected at startup), the edge redirected it to the Access login page. The binding followed that redirect back through the remote proxy, looping until it failed with TypeError: Too many redirects and an error message containing the Access login URL. Miniflare now detects the redirect, returns a readable 401 explaining how to re-authenticate, and logs the existing one-time "Cloudflare Access blocked a remote bindings request" warning.
The remote proxy server now marks the responses it forwards from a binding, so only Access responses generated in front of it are replaced. An Access login redirect or block page returned by a remote binding itself (for example, a Worker proxying an Access-protected origin) now reaches the caller unchanged.
Updated dependencies [dc35efb, dc35efb, dc35efb, dc35efb, dc35efb, b8387a5, 4cde694, b2061f4, b2061f4, f1d81a2, 4bb491b, 36e64f2, 92c4b97]:
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
34f34b3 Thanks @punkeel! - Allow opting into zstd compression for Wrangler-built container image layers with WRANGLER_CONTAINER_IMAGE_COMPRESSION=zstd.#16670 b14b9dc Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-03
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16011 44d1ee4 Thanks @wra-sol! - Offer to delete a Worker's Container applications when running wrangler delete
Previously, wrangler delete removed only the Worker, leaving the Container applications that wrangler deploy created for it running and billing. It now offers to delete them as well. With --force, or in CI and other non-interactive contexts, it lists them instead so they can be removed with wrangler containers delete <id>.
#16670 b14b9dc Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261102.1 | ^5.20261103.1 |
| workerd | 1.20261102.1 | 1.20261103.1 |
…for compatibility. These exports are deprecated and now use the implementations in @cloudflare/workers-utils . Add a dependency on that package and re…
#16642 d38cb02 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-02
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16642 d38cb02 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261101.1 | ^5.20261102.1 |
| workerd | 1.20261101.1 | 1.20261102.1 |
#16623 51bbf8b Thanks @petebacondarwin! - Deprecate shared tooling helper exports from Miniflare
Miniflare continues to export getNodeCompat, NodeJSCompatMode, and getFreshSourceMapSupport for compatibility. These exports are deprecated and now use the implementations in @cloudflare/workers-utils. Add a dependency on that package and replace the Miniflare imports with:
import {
getNodeCompat,
type NodeJSCompatMode,
} from "@cloudflare/workers-utils/node-compat";
import { getFreshSourceMapSupport } from "@cloudflare/workers-utils/sourcemap";Wrangler and the Cloudflare Vite and Vitest plugins now use the shared helpers directly. The helpers retain their behavior and can be imported without loading the Workers runtime.
The deprecated Miniflare exports will be removed in a later release, allowing downstream tools such as cf to migrate and release independently first.
#16531 e5b1798 Thanks @dario-piotrowicz! - Avoid unrelated route permission checks when comparing dashboard configuration
When a Worker was last updated from the dashboard, wrangler deploy and wrangler versions upload fetched route and custom-domain metadata even when the command could not change it. Wrangler now fetches only the route categories configured for deployment, allowing Worker-scoped Editor tokens to upload Workers without routes or custom domains.
When worker-configuration.d.ts was checked out with CRLF line endings (for example with Git's core.autocrlf=true , the default on Windows), the runtim
#16594 effe4ed Thanks @jaeminbird! - Fix wrangler types --check reporting CRLF types files as out of date
When worker-configuration.d.ts was checked out with CRLF line endings (for example with Git's core.autocrlf=true, the default on Windows), the runtime header kept a trailing \r and never matched the expected header. wrangler types --check then always failed, wrangler dev always warned that the types might be out of date, and cached runtime types were never reused. Generated types files are now read with either line ending.
#16635 76e18a8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-01
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16635 76e18a8 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261023.1 | ^5.20261101.1 |
| workerd | 1.20261023.1 | 1.20261101.1 |
#16535 5740867 Thanks @petebacondarwin! - Keep Pages development asset lookups within the configured directory
Validate resolved asset paths relative to the Pages output directory, preventing neighboring files and directories with a shared name prefix from being served. This also applies to the Vitest Pages ASSETS helper. Assets inside the directory and existing not-found fallbacks retain their behavior.
#16366 d174de8 Thanks @MattieTK! - Deploy the requested directory when wrangler pages deploy <directory> is run as a Workers static-assets deploy
When wrangler pages deploy <directory> was carried out as a Workers static-assets deploy, the <directory> argument was only used to check for unsupported Pages features and was then dropped. Autoconfig detected an assets directory of its own instead, and when the project root contained an index.html it chose the whole project root, even when a narrower directory such as public had been requested. Source files and configuration outside the requested directory that were not excluded by .assetsignore could then be uploaded as public static assets.
The requested directory is now validated before files are written and passed through to the deploy. Unconfigured projects are set up for static assets even when framework dependencies are present; existing Workers configs receive an --assets or legacy --site override. Projects configured through the Cloudflare Vite plugin alone keep their configuration and scripts, using the requested directory and an explicit or default compatibility date just for this deploy. Successful deployments without a config file are recorded in the project's .wrangler/deployments directory for that account and Worker, surviving dependency reinstalls. Repeat deploys verify the recorded version still belongs to the target Worker before allowing an update, preserving protection against name collisions and replacements.
#16562 aece4df Thanks @audricbizouarn-dashdoc! - Retry transient failures when starting a Workers assets upload session
Asset manifest registration now uses the same bounded API retry policy as Worker uploads, including support for Retry-After. Temporary server errors no longer immediately abort an otherwise valid deployment. Persistent failures still surface the original error after the retry limit; this does not repair server-side issues affecting a specific Worker.
#16603 2667a9f Thanks @petebacondarwin! - Fix repeated slashes in URL paths bypassing Pages Functions middleware
Pages Functions now collapse repeated slashes when looking up middleware, so requests such as //secure/one run the same middleware as /secure/one. The original request URL and function-route matching are preserved. Middleware receives a functionPath prefix from the original URL so imported assets can still resolve their relative paths.
#16525 ed7fb41 Thanks @petebacondarwin! - Validate OAuth error callbacks against the pending login
All authorization callbacks, including ones without a code or error, now require the matching login state. Unrelated callbacks leave the login running so the authorization page can complete it, and control characters in provider error messages are displayed as escaped text.
#16597 f9dbb22 Thanks @guybedford! - Fix WebAssembly stack frames printing as at [object Object] in source-mapped errors
WebAssembly frames in source-mapped error stack traces now show their original function and location instead of [object Object].
The database name is now optional. With no name, the command returns the top queries across every D1 database in the account, and each result gains a
#16532 25802bc Thanks @simonha9! - Allow the experimental wrangler d1 insights command to run across every D1 database in the account
The database name is now optional. With no name, the command returns the top queries across every D1 database in the account, and each result gains a databaseId field.
#16369 ec0bea4 Thanks @MattieTK! - Stop autoconfig in non-interactive runs when a project root holds both static files and a Pages functions directory
When a project without a detected framework has a functions directory, autoconfig asks whether it is a Cloudflare Pages project. Non-interactive runs (CI and coding agents) assume it is not and continue as a static site. When the static files are in the project root, that deploys the root as static assets, and the Pages Functions (the project's API routes) are not deployed.
In that case autoconfig now stops with an error explaining that Pages Functions cannot be migrated automatically yet. For Pages Functions it suggests moving the static files into a subdirectory and deploying with wrangler pages deploy, or migrating the Functions to a Worker; for a functions directory that is not Pages Functions, it suggests moving the static files into a subdirectory or adding a configuration file. Projects whose static files are already in a subdirectory, projects detected as Pages or with a detected framework, and interactive runs where the user answers the prompt are unaffected.
#16367 b4653b4 Thanks @MattieTK! - Write a protective .assetsignore when autoconfig uses the project root as the static assets directory
Autoconfig is meant to write an .assetsignore when the project root itself is the assets directory, so that local files are not uploaded as public assets. The check compared the detected output directory, which is relative ("."), with the absolute project path, so it never matched and no .assetsignore was written. A static project with an index.html at its root (for example after wrangler setup or a zero-config wrangler deploy) then uploaded files such as .env, .dev.vars, .git and node_modules as public assets.
The check now resolves the assets directory that the generated configuration uses and compares it with the project root, so frameworks that set their own build output directory (such as Nuxt or SvelteKit) do not get an unused root .assetsignore. The generated .assetsignore also covers what a Cloudflare Pages upload skips, alongside the existing .wrangler, .dev.vars* and .env* entries: /_worker.js, /_routes.json and /functions at the root (so nested paths such as blog/functions/index.html are still uploaded), node_modules, .git and .DS_Store at any depth, and .npmrc. If an existing .assetsignore only lists a narrower pattern such as .env, .env* is added so that files like .env.production are skipped too. When the project root of an assets-only project contains a Pages functions directory or _worker.js, autoconfig now warns that it will not be deployed, since it is excluded from the assets and not run as server code.
#16532 25802bc Thanks @simonha9! - Fail the experimental wrangler d1 insights command with an actionable error when the GraphQL Analytics API rejects the request
Previously the command printed an empty []. Rate limit errors now say how long to wait before retrying, and authorization errors name the "Account Analytics: Read" permission the API token needs.
#16013 8b64bec Thanks @swalker326! - Fix Durable Object self-references in tests and container validation
Durable Object bindings that explicitly name the Worker itself now resolve to the test runner in @cloudflare/vitest-plugin, for both cloudflare.config.ts and Wrangler configuration files. Named Wrangler environments use their effective Worker name, keeping bindings to the base Worker external. Container validation also accepts these self-references, using the effective deployment name to distinguish local and external bindings.
Explicit binding targets remain intact during configuration conversion, so deploying with --name or a CI name override preserves the intended Durable Object target.
Setting remote: true on an Analytics Engine dataset now sends writeDataPoint() calls from wrangler dev and the Vite plugin to the real dataset. Withou
#16536 a95d647 Thanks @WalshyDev! - Support remote Analytics Engine bindings in local development
Setting remote: true on an Analytics Engine dataset now sends writeDataPoint() calls from wrangler dev and the Vite plugin to the real dataset. Without it, writes are still dropped locally.
{
"analytics_engine_datasets": [
{
"binding": "EVENTS",
"dataset": "my-dataset",
"remote": true
}
]
}#16526 dba0e81 Thanks @petebacondarwin! - Render terminal control characters as visible text in tail output
Pretty tail and remote-preview output now escape control characters in log strings, exceptions and event metadata. Unicode, tabs and multiline logs remain readable, and JSON output keeps the original structured values.
#16489 fc57bc0 Thanks @akshitsinha! - Keep Flagship flag metadata when updating flags
wrangler flagship flags commands that update an existing flag, such as enable, set, rollout, split, and rules, no longer clear the flag's metadata. wrangler flagship flags pull now copies metadata into the local flag store.
#16521 ec6eddd Thanks @petebacondarwin! - Validate .assetsignore encoding before building asset manifests
Asset uploads and local development now stop with an actionable user error when .assetsignore is not valid UTF-8 or contains null characters, instead of silently losing its patterns. This also applies to standalone Miniflare and the Wrangler, Vite and Vitest development integrations. Save the file as UTF-8 to continue; UTF-8 files with a byte order mark and intentionally empty files remain supported.
In Miniflare v5 beta, resolve the registry from CLOUDFLARE_DEV_REGISTRY_PATH , then the unsafeDevRegistryPath constructor option, then <Cloudflare con
#16494 0968b08 Thanks @petebacondarwin! - Enable Miniflare's development registry by default and centralize path resolution
In Miniflare v5 beta, resolve the registry from CLOUDFLARE_DEV_REGISTRY_PATH, then the unsafeDevRegistryPath constructor option, then <Cloudflare config directory>/dev-registry/v5. The default is independent of legacy Wrangler directories and is scoped to the Miniflare major version. The Vite v2 beta plugin follows this new default, while current Wrangler and getPlatformProxy() retain Wrangler's legacy default for compatibility with existing Wrangler sessions. Vite v2 and Wrangler therefore require the same CLOUDFLARE_DEV_REGISTRY_PATH to discover each other; set it for both processes when mixing these tools.
Add enableDevRegistry: false to disable registration and discovery explicitly. Shared storage now uses the resolved default without requiring an explicit path. As before, shared storage requires an enabled registry to elect a storage owner, so combining unsafeEnableSharedStorage: true with enableDevRegistry: false is rejected. Miniflare no longer reads MINIFLARE_REGISTRY_PATH; use CLOUDFLARE_DEV_REGISTRY_PATH instead. Expose resolveDevRegistryPath() for integrations that also read registry files. Wrangler uses the effective path for its runtime configuration, initial bindings display, and Flagship active-session check, so the canonical override cannot bypass that check. An explicitly disabled Wrangler registry remains disabled.
#16499 f3c13b3 Thanks @dinasaur404! - Preserve binding error codes and names in local development
Errors from remote bindings and from Node.js binding proxies (getPlatformProxy() and Miniflare#getBindings()) now keep their machine-readable properties, such as Artifacts' code and numericCode. Previously these properties were dropped and the error name was folded into the message (for example "ArtifactsError: Repository not found"), so code could only branch on error text during local development.
Node.js callers also keep custom error names such as ArtifactsError. Errors from remote bindings received inside a Worker keep their properties but are still named Error.
When a config has routes , local dev infers the origin from the first route, so the Worker sees request.url , the Host header, and any Origin header r
#14865 c0e915f Thanks @TheSaiEaranti! - Add an --infer-origin-from-routes flag to wrangler dev
When a config has routes, local dev infers the origin from the first route, so the Worker sees request.url, the Host header, and any Origin header rewritten to the route's host even though the client connected to localhost. That silently breaks Host/Origin-sensitive logic — for example a CORS check allowlisting http://localhost:* receives http://<route-host> instead and rejects the request only in local dev.
The inference is intentional and remains the default. Passing --infer-origin-from-routes=false now opts out, preserving the real local origin without removing routes from the config. An explicitly configured --host, --local-upstream, or dev.host continues to take precedence either way. The flag only affects local development: in remote mode the route host still determines the preview session as before.
#15955 23ef63a Thanks @ericclemmons! - Expand dotenv variable references in --secrets-file input
Dotenv files supplied through --secrets-file to deploy, versions upload, and preview now expand $VAR and ${VAR} references using process values and earlier file values. Process environment values override matching file keys, including explicitly empty values. Treat dotenv secrets files as trusted input: they can read and upload any process environment value, such as a CI credential referenced by X=${GITHUB_TOKEN}. In CI, use secrets files whose contents untrusted contributors cannot modify.
This changes how existing dotenv secrets files are interpreted: an unset reference becomes an empty string, so PASSWORD=pa$word becomes pa when word is unset. Escape literal dollar signs with a backslash (PASSWORD=pa\$word), or use a JSON secrets file to preserve values exactly. JSON input and bulk-secret commands, including piped stdin, retain their existing literal parsing.
#16403 5f82a56 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-10-22
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16437 e651d7c Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-10-23
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16403 5f82a56 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261019.1 | ^5.20261022.1 |
| workerd | 1.20261019.1 | 1.20261022.1 |
#16437 e651d7c Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261022.1 | ^5.20261023.1 |
| workerd | 1.20261022.1 | 1.20261023.1 |
#16476 8a30d8e Thanks @tannerlinsley! - Update Undici to 7.30.1 to prevent a malformed HTTP response from crashing development tools
The updated shared dependency rejects excessive content encodings without leaving an unhandled stream error when the server closes the connection early. This fixes GHSA-xjj6-f33q-929c and keeps the matching Undici types on the same version.
#16485 b7e762d Thanks @Cherry! - Fix the Windows keyring install when the config path contains a space
On Windows, wrangler login --use-keyring could not set up keyring storage when the configuration path contained a space, such as a C:\Users\John Smith profile, so credentials fell back to the plaintext file. Keyring setup now works for those paths and credentials are stored encrypted.
#16405 c709bff Thanks @ondraulehla! - Fix kv key list returning only the first 1000 keys in local mode
Listing a local namespace with more than 1000 keys stopped after the first 1000 without any warning, so the output looked complete when it wasn't. kv key list now returns every key in local mode, with or without --prefix.
#16490 bcd618d Thanks @petebacondarwin! - Update Zod to 4.6.6 to address GHSA-mrhx-c7xc-m3w5
The updated shared dependency fixes excessive memory consumption when validating oversized collections. This updates both the published Zod dependencies and the copies bundled into development tools and Workers.
Updated dependencies [9e05ade, 5f82a56, e651d7c, 5f82a56, e651d7c, 8a30d8e, bcd618d]:
`jsonc { "hyperdrive": [ { "binding": "HYPERDRIVE", "id": " ", "remote": true } ] } `
#14900 08f22d3 Thanks @mack-erel! - Support remote Hyperdrive bindings in local development
{
"hyperdrive": [
{
"binding": "HYPERDRIVE",
"id": "<your-hyperdrive-id>",
"remote": true
}
]
}
#16357 182d6de Thanks @Naapperas! - Add a jurisdiction setting to Workflows
A Workflow defined by the Worker can now set the jurisdiction that its instances run and store their data in, on either a workflows binding or a workflow export:
{
"workflows": [
{
"binding": "MY_WORKFLOW",
"name": "my-workflow",
"class_name": "MyWorkflow",
"jurisdiction": "eu"
}
]
}
The accepted values are eu, fedramp, and us. wrangler deploy and wrangler triggers deploy send the jurisdiction when they create or update the Workflow. A Workflow's jurisdiction is set when it is created and cannot be changed afterwards, so wrangler deploy and wrangler versions upload stop before uploading when an existing Workflow has a different jurisdiction from the configured one. Leaving jurisdiction out keeps the Workflow's existing jurisdiction. @cloudflare/config adds the setting to exports.workflow(), cf migrate carries it over, and wrangler workflows describe prints it. Local development ignores it.
#16388 80a9f96 Thanks @DevVettel! - Print wrangler auth token --json output regardless of WRANGLER_LOG
Previously the JSON was written through the normal log channel, so setting WRANGLER_LOG to warn, error or none made the command exit successfully with empty stdout. Tools that parse this output, such as the OpenNext Cloudflare adapter in CI, then failed to find any credentials. The JSON is now always printed, like other --json commands.
#16361 2878645 Thanks @GrosserNL! - Report the R2 bucket location returned by the API when creating a bucket
wrangler r2 bucket create --location printed the requested location hint even when R2 ignored it. Recreating a deleted bucket name keeps the original location, so the success message could claim a placement the bucket does not have. The command now uses the location from the create response: it mentions the hint only when that location matches, and otherwise reports the location R2 actually applied.
Updated dependencies [08f22d3, a4eb57d]:
Previously, wrangler dev failed to start module Workers that exported only named entrypoints, such as RPC services, unless an unused default export wa
#15611 4508172 Thanks @taylorlee! - Allow wrangler dev to start module Workers without a default export
Previously, wrangler dev failed to start module Workers that exported only named entrypoints, such as RPC services, unless an unused default export was added. These Workers now start normally in local development without that workaround.
#16370 61fc739 Thanks @WalshyDev! - Fetch the remote config diff from the configured compliance region
When a Worker was last deployed from the dashboard, wrangler deploy and wrangler versions upload download its remote configuration to compare with the local one. These requests ignored the compliance_region field in the Wrangler configuration file and only honoured the CLOUDFLARE_COMPLIANCE_REGION environment variable. A FedRAMP High Worker configured through the config file would send them to api.cloudflare.com instead of api.fed.cloudflare.com, and the deploy would fail with authentication errors. They now use the same compliance region as the rest of the deploy.
#15846 a88cac4 Thanks @oddharsh! - Fail with an error instead of hanging when local dev requests can't work under Bun
Bun's fetch() ignores the undici dispatcher that Miniflare routes requests through (oven-sh/bun#39247). Under Bun, createTestHarness()'s server.fetch() and server.getWorker()'s fetch(), email() and scheduled() now throw a UserError, requests to the dev server URL get a 503 naming the cause, and starting remote bindings throws a UserError. Each of these used to hang with no error. server.getWorker().getEnv() and getExport() keep working under Bun.
#16359 262021d Thanks @tw4! - Stop --strict deploys and version uploads from aborting when the API omits optional binding fields
Previously, wrangler deploy --strict and wrangler versions upload --strict could report a destructive change for an unchanged configuration, for example an R2 bucket in the default jurisdiction, because a field the API left out was compared as removed. Missing and unset optional fields are now treated as equal, so these commands proceed when the local configuration matches the deployed Worker.
Updated dependencies [3464abc]:
The following dependency versions have been updated:
#16307 37ab91c Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261006.1 | ^5.20261016.1 |
| workerd | 1.20261012.1 | 1.20261016.1 |
#16352 0ae7926 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261016.1 | ^5.20261019.1 |
| workerd | 1.20261016.1 | 1.20261019.1 |
wrangler dev --remote and getPlatformProxy() refresh their preview token before it expires, but a single failed refresh — for example while the networ
#15541 e13d5cc Thanks @mack-erel! - Keep remote dev sessions alive through transient network failures
wrangler dev --remote and getPlatformProxy() refresh their preview token before it expires, but a single failed refresh — for example while the network was briefly down — stopped refreshing for good, leaving the session broken until restart. A failed refresh now retries every minute until it succeeds. Rebuilds also no longer push the refresh past the session's expiry.
#16284 42c6912 Thanks @karloper! - Fix wrangler rollback reporting success after the changed secrets confirmation is declined
Previously, declining the "The following secrets have changed…" confirmation printed "Aborting rollback..." and then also printed a success message and the target version as the "Current Version ID", even though no deployment was made and the original version was still live. Wrangler now stops after aborting, so the output matches what is actually deployed.
#13742 4a5377f Thanks @edmundhung! - Hide the wrangler dev hotkey bar when Turborepo does not forward input
Updated dependencies [e1d1b77]:
Build Output now matches wrangler deploy and wrangler versions upload , which upload source maps by default, so Workers built for tools like cf get st
#16245 d6b1c82 Thanks @WalshyDev! - Include source maps by default in wrangler build --experimental-cf-build-output
Build Output now matches wrangler deploy and wrangler versions upload, which upload source maps by default, so Workers built for tools like cf get stack traces that point at the original source. Source maps that can't be resolved are skipped rather than failing the build. Set upload_source_maps = false to opt out.
#16220 97b2fb1 Thanks @FlorentCollin! - Support local D1 queries through the experimental d1_binding_jsrpc compatibility flag
Local D1 bindings now implement the RPC query backend used by D1Database.query() and prepared-statement methods when the flag is enabled. Queries reuse local SQLite execution, including transactional batches, execution metadata, and session bookmarks, while bindings without the flag continue to use HTTP. Update the bundled workerd runtime to 1.20261012.1 and align the default compatibility date with that release.
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 w
#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.
#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.
…latest on npm, even after that version had been deprecated for shipping a bug. Deprecated versions are now never recommended: if the latest release ha…
#16036 9a58244 Thanks @edevil! - Support temporary event accounts in R2 and Containers commands
wrangler r2 and wrangler containers commands now accept the hidden --temporary flag, so accounts created for an event can manage buckets, objects and containers directly. Every command that supports --temporary now also accepts a hidden --event-code flag, so the first command a participant runs can create the event account:
wrangler r2 bucket create my-bucket --temporary --event-code <code>
R2 and Containers are only available on event accounts. R2 custom domains, Sippy, external container registries and wrangler cloudchamber commands still require a logged-in account.
#16139 2d1d563 Thanks @cpojer! - Update esbuild to 0.28.2
Align esbuild dependency with tooling using the latest 0.28 patch so package managers can share one installation instead of downloading a second native binary.
#15632 85b14e7 Thanks @petebacondarwin! - Honor Retry-After directives during static asset uploads
Static asset uploads now pause retries and pending uploads until the latest outstanding deadline requested by the API. A per-request limiter also keeps gateway retries at the reduced concurrency after the pause ends, preventing a deployment from immediately overloading a constrained asset service again.
#16098 fe607f9 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| sharp | 0.35.4 | 0.35.5 |
#16093 ad7ff45 Thanks @DiogoSantoss! - Document that addresses catch-all entries must use the zone apex
A *@domain entry in addresses must use the zone apex, such as *@example.com. The zone catch-all also receives mail for every subdomain in the zone that has no literal rule.
#16102 757faa6 Thanks @tlq5l! - Keep Preview secrets when deploying to an existing Preview
Secrets added to a Preview with wrangler preview secret put or wrangler preview secret bulk were lost the next time wrangler preview ran, because each new deployment was created from the Wrangler config, --var and --secrets-file values only.
wrangler preview now carries over the secrets of the Preview's latest deployment. A value passed in this deployment (--secrets-file, --var or a previews binding with the same name) still replaces the existing secret, and wrangler preview secret delete removes one.
#15617 93c1069 Thanks @jpatel3! - Stop the update check from recommending deprecated versions
Previously, the "update available" notice shown by wrangler and @cloudflare/vite-plugin always pointed at whichever version was tagged latest on npm, even after that version had been deprecated for shipping a bug. Deprecated versions are now never recommended: if the latest release has been deprecated, the newest non-deprecated stable release below it is suggested instead, or nothing at all if you are already on it.
The check now reads the npm registry directly instead of going through the update-check package, which discarded the deprecation information. The on-disk cache location and one-hour refresh interval are unchanged.
#16003 6947df3 Thanks @oddharsh! - Ship using and await using declarations to the runtime as written, for smaller Worker bundles
Workers and Pages Functions that use explicit resource management no longer carry about 1 KB of bundled helper code to emulate it. workerd supports using and await using natively at every compatibility date, so wrangler deploy, wrangler versions upload and Pages Functions builds now leave these declarations untouched.
#15958 82acf3c Thanks @breken-ai! - Apply each action's own condition in wrangler r2 bucket lifecycle add
When a lifecycle rule was added with both expiration and Infrequent Access transition flags, both actions read their condition from the same list of flags, which checked --expire-days first. --expire-days 365 --ia-transition-days 30 therefore transitioned objects after 365 days instead of 30, and --expire-date 2027-01-01 --ia-transition-days 30 deleted objects after 30 days instead of on the given date. Expiration now only reads --expire-days/--expire-date, and transition only reads --ia-transition-days/--ia-transition-date.
Updated dependencies [2d1d563, e6f7663, fe607f9, 8de6b3c, ae29445, cc8e969, 417b186]:
The Event Subscriptions API requires source.namespace and source.repo_name for artifacts.repo subscriptions, but Wrangler had no way to pass them, so
#16051 b4e1299 Thanks @devteamaegis! - Add --source-namespace and --source-repo-name to wrangler queues subscription create for the artifacts.repo source
The Event Subscriptions API requires source.namespace and source.repo_name for artifacts.repo subscriptions, but Wrangler had no way to pass them, so --source artifacts.repo always failed with a validation error. Both flags are now required for this source, and wrangler queues subscription get shows the subscription's resource as <namespace>/<repo-name>.
#15998 b75421f Thanks @dario-piotrowicz! - Add assets.base_path support to Workers Assets
Serve an asset directory from a public URL prefix without changing its on-disk layout:
{
"assets": {
"directory": "./public",
"base_path": "/docs"
}
}Wrangler, preview, Miniflare, and generated build configuration preserve the explicitly selected value, while the Asset Worker normalizes it and strips the prefix only for asset lookup. Requests passed to a user Worker, request-facing headers, and redirects retain the public path. Relative pathname inputs are interpreted as root-relative prefixes, URL-shaped values are rejected, and omitting the option preserves existing root-path behavior.
Authored _headers and _redirects rules continue to match full public paths. In particular, both the source and destination of an authored 200 asset rewrite must include the configured public prefix; Asset Worker-generated redirects are prefixed automatically.
#16005 4d308f6 Thanks @oOPa! - Add a --experimental-mode instant option to wrangler kv namespace create
This lets entitled accounts create Workers KV Instant namespaces while the feature is in private beta.
#16030 aa2f9b7 Thanks @edmundhung! - Add email-protected Quick Tunnels to wrangler dev
Pass one or more --tunnel-allowed-mail flags to require email authentication when exposing a local development server through a Quick Tunnel. Each value can be an exact email address or a domain pattern.
#15283 2dde890 Thanks @shubhxho! - Support deleting secrets with wrangler versions secret bulk
Set a secret's value to null in JSON input to remove it from the new Worker version. Bulk output now distinguishes between created and deleted secrets, so retrying wrangler secret bulk with wrangler versions secret bulk preserves requested deletions. Deploy the new version with wrangler versions deploy to apply the changes to production traffic.
#15534 2b1a0ca Thanks @vahidshaik1901! - Improve guidance for conflicting Wrangler configuration files
When user and generated deploy configurations are found under different base paths, Wrangler now identifies the expected deploy configuration location, suggests how to resolve the conflict, and links to the relevant documentation.
#16014 c492d63 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261001.1 | ^5.20261005.1 |
| workerd | 1.20261001.1 | 1.20261005.1 |
#16079 ba52118 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20261005.1 | ^5.20261006.1 |
| workerd | 1.20261005.1 | 1.20261006.1 |
#15573 14f0339 Thanks @xgame92! - Include default module rules in generated Worker types
wrangler types now declares the built-in Text, Data, and WebAssembly module patterns even when they are not repeated in the Wrangler configuration, keeping generated types aligned with deployment behavior.
Service-worker declaration files are emitted as global scripts so that the generated wildcard module types are visible to imports.
Directory-specific rules retain their scope when TypeScript can represent it; ambiguous relative imports use a union of the possible deployed module types.
When generating combined types for named environments, each environment's effective rules are resolved independently and differing import types are represented as unions.
#15261 42c7219 Thanks @ondraulehla! - Fix r2 object put and r2 bulk put storing a different key in local mode
Keys that are not URL-safe were mangled on the way into local storage.
r2 object get for that key reported that the key does not exist.# collapsed into a single object, and the second upload replaced the first.% that is not a valid escape failed outright with "Invalid URL string.", and one with a valid escape, such as %41.txt, was stored as A.txt.Spaces, non-ASCII characters, # and % now survive the trip into local storage. Objects already in local state are left where they are.
#15283 2dde890 Thanks @shubhxho! - Show a useful error when wrangler secret bulk hits an undeployed latest version
wrangler secret put already explained this case (API error 10215). secret bulk just dumped the raw API response, which for 10214 talks about logpush and tail_consumers even though you were only uploading secrets.
Both commands now point at wrangler versions secret … instead.
#16068 26e03e2 Thanks @edevil! - Print temporary account notices to stderr
The terms notice, the proof-of-work message, and the "Temporary account ready" claim details printed by --temporary now go to stderr instead of stdout. Previously they corrupted command output on stdout, such as the JSON from wrangler kv namespace list --temporary or the raw value from wrangler kv key get --temporary. Commands that lower the log level for --json, such as wrangler d1 execute --json --temporary, also hid the claim URL; it is now shown unless logging is disabled with WRANGLER_LOG=none.
Scripts that read the claim URL from stdout should read stderr instead.
Updated dependencies [b75421f, 0ec13b7, c492d63, ba52118, 946aaa7, 48f3c04, 5606a74, f8cdcb9, e44cf6b, 0b51fec]:
Container placement constraints now accept constraints.jurisdiction: "us" in Wrangler and typed Cloudflare configuration. This makes the US jurisdicti
#15928 7f57b1c Thanks @ichernetsky-cf! - Allow "us" as a jurisdiction for Container applications
Container placement constraints now accept constraints.jurisdiction: "us" in Wrangler and typed Cloudflare configuration. This makes the US jurisdiction available alongside "eu" and "fedramp".
#15974 7f700ef Thanks @martinezjandrew! - Fix wrangler containers list to report live instances
The LIVE INSTANCES column now reports each application's active runtime instances instead of its configured instance count, matching the Cloudflare dashboard. JSON output continues to expose the configured count through the existing instances field.
#15980 90e6a1b Thanks @martinezjandrew! - Accept Durable Object application IDs in Containers commands
wrangler containers instances and wrangler containers delete now accept the 32-character hexadecimal application IDs returned for Durable Object-backed applications, in addition to legacy dashed UUIDs.
#15871 6a4b0fe Thanks @tw4! - Retry transient API failures in wrangler workflows instances list and wrangler workflows instances describe
Previously, a single temporary 5xx response or dropped connection made these read-only commands exit with an error, even though the next request would have succeeded. They now use Wrangler's existing bounded API retry handling. The read that resolves --id latest is retried too, which also benefits the other wrangler workflows instances commands that accept latest; the mutating requests they make afterwards are not retried. Persistent failures are still reported after the retries are exhausted, and under --json any retry notices are written to stderr so stdout stays valid JSON.
Updated dependencies []:
…matching the runtime API while preserving the deprecated array form.
#15777 464a582 Thanks @Naapperas! - Support the new Workflows createBatch() API in local development
Local Workflows bindings now accept object-form batches that create instances from a count or a list of instance options. The result includes handles for created instances and indexed per-instance errors, matching the runtime API while preserving the deprecated array form.
#15639 aee2842 Thanks @hugo-vicente11! - Add --allowed-mail to the experimental wrangler tunnel quick-start command
The option forwards exact email addresses, comma-separated lists, and wildcard domains to cloudflared. It can be specified more than once to combine multiple recipient rules.
Email-protected tunnels require cloudflared 2026.9.2 or later. Wrangler checks the selected binary before starting the tunnel and reports an upgrade error when it is incompatible.
#15992 b8e7cc3 Thanks @zebp! - Mark wrangler artifacts commands as open beta
Artifacts has entered open beta, so the wrangler artifacts commands no longer display a "private beta" label in help output and warnings.
#15984 9d7b08e Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260930.2 | ^5.20261001.1 |
| workerd | 1.20260930.2 | 1.20261001.1 |
#15959 efd67e6 Thanks @breken-ai! - Keep colons in wrangler tail --header filter values
wrangler tail --header splits its argument into a header name and an optional value at the colon. It split at every colon and kept only the first two parts, so a value containing a colon was cut short: --header "Origin:https://app.example.com" filtered on https. The value now includes everything after the first colon, so URLs, ports and IPv6 addresses are sent to the tail filter intact.
Declare the zero-configuration binding in wrangler.json with "analytics": { "binding": "ANALYTICS" } . Wrangler uploads the analytics binding type and
#15685 b9f1cdc Thanks @Ankcorn! - Add native support for the Analytics SQL binding
Declare the zero-configuration binding in wrangler.json with "analytics": { "binding": "ANALYTICS" }. Wrangler uploads the analytics binding type and proxies it to the remote service during local development, so wrangler dev can call the binding without unsafe.bindings.
#15943 8468487 Thanks @sejoker! - Graduate SQL, Catalog, and Pipelines under wrangler basin out of beta to stable
Basin SQL is now available under wrangler basin sql, Basin Catalog operations are available under wrangler basin catalog, and Pipelines operations are available under wrangler basin pipelines. These commands are now stable, while the previous wrangler r2 sql, wrangler r2 bucket catalog, and wrangler pipelines command paths remain available as hidden compatibility aliases.
The Basin SQL authentication environment variable is now WRANGLER_BASIN_SQL_AUTH_TOKEN. Update any existing WRANGLER_R2_SQL_AUTH_TOKEN configuration to use the new name. The fallback to CLOUDFLARE_API_TOKEN remains available.
#15948 a0712e5 Thanks @akoval-cf! - Add beta K2 producer bindings for existing streams
Configure a stream created through Wrangler, the Dashboard, or the API in wrangler.json:
{
"k2": [
{
"binding": "ORDERS",
"stream": "0123456789abcdef0123456789abcdef"
}
]
}The binding supports env.ORDERS.send([{ content: new TextEncoder().encode("order"), headers: { event: "order.created" } }]). Batches use either all ArrayBuffer or all Uint8Array content. Check the returned success value, handle rejected RPC promises, and retry only when the returned error explicitly allows it. Generated environment types describe this producer contract without requiring a separate application dependency.
K2 requires an enabled account. Deployment credentials need Worker deployment and K2 configuration-read access. Default Wrangler logins now request the K2 OAuth scopes; existing OAuth users should run wrangler login again to grant the new permissions. Development always uses a real K2 stream and may incur usage charges; no local simulator is provided. The remote setting can be omitted, remote: true suppresses the usage warning, and remote: false is rejected. Consumption is not part of this Worker binding.
#15948 a0712e5 Thanks @akoval-cf! - Add beta K2 stream management commands
Use wrangler k2 streams create order_events, wrangler k2 streams list, wrangler k2 streams get <stream-id>, and wrangler k2 streams delete <stream-id> to manage K2 streams. Creation enables Worker bindings but not HTTP ingestion by default, matching the dashboard. Pass --http-enabled to enable authenticated HTTP ingestion and print its endpoint. Creation prints the stream ID and a binding configuration with a YOUR_BINDING_NAME placeholder for the Worker's variable name, but does not edit the configuration file automatically.
All four commands support --json. Deletion requires confirmation, or --force/-y to skip it; use --force --json for JSON deletion output. Creation also accepts retention, HTTP authentication, Worker-input, and CORS options; listing supports pagination and a name filter. Default Wrangler logins now request k2.read and k2.write; existing OAuth users should run wrangler login again, or use a custom API token granting K2 Config Write. The account must be enabled for K2.
#15908 ddaa558 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260926.1 | ^5.20260930.2 |
| workerd | 1.20260926.1 | 1.20260930.2 |
OpenSSH only allocates a pseudo-terminal when no remote command is given, so interactive commands such as wrangler containers ssh <ID> -- bash previou
#15919 91a3606 Thanks @flakey5! - Add --tty (-t) flag to wrangler containers ssh to force pseudo-terminal allocation
OpenSSH only allocates a pseudo-terminal when no remote command is given, so interactive commands such as wrangler containers ssh <ID> -- bash previously ran without a prompt or line editing. Pass --tty to force one:
wrangler containers ssh <ID> --tty -- bash
#15951 2a15ae2 Thanks @flakey5! - Support SSH settings for Durable Object-managed Containers in the configuration API
defineContainer now accepts ssh and authorizedKeys with schedulingPolicy: "durable-object", matching the ssh and authorized_keys fields that Wrangler already supports for these Containers. Previously the schema rejected them, so they could not be set from cloudflare.config.ts.
defineContainer({
name: "sandbox",
schedulingPolicy: "durable-object",
ssh: { enabled: true },
authorizedKeys: [{ name: "laptop", publicKey: "ssh-ed25519 AAAA..." }],
});Running wrangler dev with remote bindings on an unpublished worker protected by Access (e.g. using a wildcard on your workers.dev domain) previously f
#15159 7bb6eae Thanks @veggiedefender! - Fix wrangler dev remote bindings for workers.dev subdomains protected by Access
Running wrangler dev with remote bindings on an unpublished worker protected by Access (e.g. using a wildcard on your workers.dev domain) previously failed with a redirect loop. Wrangler now correctly authenticates remote bindings with Access in this situation.
#15923 60ccdbd Thanks @petebacondarwin! - Upgrade the bundled capnweb implementation to 0.12.0
This updates the RPC implementation shipped in Miniflare and remote-binding proxy workers to the latest capnweb release.
#15938 62fd03a Thanks @dieub! - Resolve the affected Undici dependency in new Wrangler and Vite plugin installs
Undici 7.29.1 fixes GHSA-3wwx-pv8p-q78v. Update the shared dependency catalog and matching types used by Miniflare and Wrangler so downstream installs can resolve the patched runtime without an application-level override. A published release is still required for consumers; this changeset does not alter already published package metadata.
#15903 06ed9c8 Thanks @itsmunzir! - Fix custom-domain-only deploys failing for API tokens without Zone Workers Routes read permission
When workers_dev was disabled and routes contained only entries with custom_domain: true, every deploy after the first one fetched /zones/:zoneId/workers/routes to check for route conflicts, even though custom domains are not zone Workers Routes. Tokens scoped to Workers Scripts edit plus custom domains - without Zone > Workers Routes > Read - failed with "No access to the specified resource" after the Worker version had already been uploaded. The conflict check now only covers non-custom-domain routes; custom domain conflicts continue to be reported by the custom domains changeset API.
#15887 86211fe Thanks @alepacheco! - Report an unreachable auth server instead of an expired login when refreshing an OAuth token
When the OAuth token endpoint could not be reached (for example a DNS failure or a connection timeout), the refresh failure was reported as "Your auth token has expired and could not be refreshed", with advice to run wrangler login; in an interactive terminal Wrangler also started a new browser login. A network failure says nothing about the stored refresh token, and a new login would need the same unreachable server. Wrangler now reports that the Cloudflare auth server could not be reached, leaves the stored credentials unchanged, and does not start a login, so the next run can refresh with the same token once the network is back.
Updated dependencies [60ccdbd, 62fd03a, c2bb4c8, eb1efe0, 485cfb3]:
Experimental cloudflare.config.ts projects must now import defineConfig , bindings, triggers, and related helpers from cf/config . Generated declarati
#15914 7f0734c Thanks @jamesopstad! - Use cf/config for cloudflare.config.ts authoring
Experimental cloudflare.config.ts projects must now import defineConfig, bindings, triggers, and related helpers from cf/config. Generated declarations from Wrangler and the Vite plugin also reference this package, so projects using the experimental configuration flow must add cf as a dependency.
The Vite plugin no longer exports @cloudflare/vite-plugin/experimental-config. wrangler/experimental-config remains available for defineWranglerConfig, but no longer re-exports Cloudflare configuration helpers.
A Workflow declared in a Worker's exports is now available on ctx.exports in wrangler dev , the Vite plugin and the Vitest plugin, with the same API a
#15856 4c2993b Thanks @Naapperas! - Support Workflows declared in exports on ctx.exports in local development
A Workflow declared in a Worker's exports is now available on ctx.exports in wrangler dev, the Vite plugin and the Vitest plugin, with the same API as a Workflow binding:
const instance = await ctx.exports.MyWorkflow.create({
params: { name: "World" },
});ctx.exports and workflows bindings with the same Workflow name share their instances, including instances created before the Workflow was declared in exports. Two Workers can't export the same Workflow name, and a binding to an exported Workflow must refer to the Worker and class that export it. getPlatformProxy() ignores Workflows declared in exports, since it doesn't run the Worker's code.
wrangler workflows commands run with --local also work with Workflows declared only in exports, without a workflows binding.
In the Vitest plugin, introspectWorkflow() and introspectWorkflowInstance() still need a Workflow binding, and now explain how to add one when passed a Workflow from ctx.exports. Instances created through ctx.exports are introspected too. A workflows binding whose script_name is the Worker's own name now resolves to the Worker itself again.
#15891 8dc53ae Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260925.1 | ^5.20260926.1 |
| workerd | 1.20260925.1 | 1.20260926.1 |
Use --durable-objects-code-update-mode immediate with wrangler deploy , wrangler versions deploy , and wrangler rollback to update code without waitin
#15658 8280086 Thanks @jqmmes! - Add Durable Objects code update strategies to Worker deployments
Use --durable-objects-code-update-mode immediate with wrangler deploy, wrangler versions deploy, and wrangler rollback to update code without waiting for active instances to hibernate. Use --durable-objects-code-update-mode deferred 30s to set a maximum delay, or configure durable_objects.code_update_strategy with mode and max_delay. When unset, the strategy defaults to deferred with a 5-minute maximum delay; delays cannot exceed 24 hours and must use millisecond precision.
#15800 bd56b98 Thanks @Refaerds! - Add Browser Run as an event source for Queue subscriptions
You can now create Queue subscriptions with --source browserRun.
#15864 ee2b200 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260923.1 | ^5.20260925.1 |
| workerd | 1.20260923.1 | 1.20260925.1 |
#15207 805af2f Thanks @exKAZUu! - Show the stack and cause of failed proxied requests in wrangler dev debug logs
When a request proxied to the local Worker fails, running with --log-level debug now shows the underlying error's stack and cause chain.
Minor Changes #15822 8f7916c Thanks @GregBrimble ! - Support Containers in Worker Preview deployments with the Build Output. Patch Changes Updated dep
8f7916c Thanks @GregBrimble! - Support Containers in Worker Preview deployments with the Build Output.Set containers[].ssh and containers[].authorized_keys when using scheduling_policy: "durable_object" . These are application-wide settings that follow
#15792 479e1e8 Thanks @flakey5! - Configure SSH for experimental Durable Object-managed Containers
Set containers[].ssh and containers[].authorized_keys when using scheduling_policy: "durable_object". These are application-wide settings that follow the same rules as the existing Durable Object-managed Container settings: normal deployments create missing applications and update explicitly configured values, while omitted settings preserve the existing application configuration.
// wrangler.jsonc
{
"containers": [
{
"name": "sandbox",
"class_name": "Sandbox",
"scheduling_policy": "durable_object",
"ssh": { "enabled": true },
"authorized_keys": [
{ "name": "laptop", "public_key": "ssh-ed25519 AAAA..." }
]
}
]
}#15648 52c0e9f Thanks @tpmmorris! - Expose configured Cron Triggers to local development consumers
Wrangler now passes the active environment's exact Cron Trigger expressions to Miniflare so Local Explorer can display them. Headless agent sessions also advertise the Local Explorer scheduled invocation API.
#15786 bdda4c3 Thanks @ThomasRubini! - Support UDP connect handlers in local development
The experimental connect configuration now accepts protocol: "udp", with optional idle_timeout_ms and max_pending_bytes settings. UDP datagrams are delivered to the Worker's connect() handler using workerd's value-mode socket streams, and can be tested with Miniflare#dispatchConnect({ protocol: "udp" }).
#15779 fc3cbaa Thanks @Naapperas! - Support workflow entries in the exports configuration map
A Worker can now declare the Workflows it defines in exports, keyed by the WorkflowEntrypoint class name:
{
"exports": {
"MyWorkflow": {
"type": "workflow",
"name": "my-workflow",
"limits": { "steps": 100 },
"schedules": "0 * * * *"
}
}
}A workflow export accepts the same settings as a workflows binding: limits, concurrency, schedules, and default_retention. wrangler deploy and wrangler versions upload send these entries to the upload API by name, and wrangler deploy and wrangler triggers deploy provision the Workflow with its settings, just as they do for workflows bindings owned by the Worker. A Workflow may be declared both as a binding and as an export, as long as both declarations use the same class and do not set the same setting to different values. A binding to another Worker's Workflow cannot share a name with an export. @cloudflare/config adds the matching exports.workflow() helper. Local development does not yet act on these entries.
#15796 be72815 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260921.1 | ^5.20260923.1 |
| workerd | 1.20260921.1 | 1.20260923.1 |
#14847 940c692 Thanks @TheSaiEaranti! - Emulate the deterministic-ID uniqueness contract in the local Workflows binding
The local Workflows binding now matches the documented production behavior for deterministic instance IDs: create({ id }) with an ID that already exists throws (instance.already_exists) and retains the existing instance, and createBatch() skips IDs that already exist or repeat within the batch, excluding them from the result instead of creating duplicate executions. Previously both paths silently created duplicates, so code relying on deterministic IDs for idempotency (for example a Queue consumer creating one workflow per message) appeared to work locally while double-executing workflow bodies.
#15803 cd60c9c Thanks @pmiguel! - Show --jurisdiction in help for wrangler kv namespace create
The option was supported but omitted from the command's help output. Users can now discover how to create KV namespaces in a specific jurisdiction.
#15838 15799d4 Thanks @oddharsh! - Update smol-toml to 1.9.0 to fix slow parsing of very large TOML files
Parse time for TOML config files now grows linearly with their size, instead of with its square: a 40,000-line file that took 259 ms to parse now takes 17 ms, while typical wrangler.toml files parse in the same time as before. This addresses the GHSA-r4xh-jqrq-34v2 advisory against earlier versions of the parser.
Some TOML syntax errors now point at the character that caused them. For example, a wrangler.toml containing INVALID "FILE is now reported as illegal character in key at the ", rather than incomplete key-value at the start of the line.
Updated dependencies [52c0e9f, 44f5295, be72815, 940c692, bdda4c3, fc3cbaa]:
Use wrangler deploy --temporary --event-code <code> to provision an account for an event. Wrangler requires explicit server acknowledgement before cac
#15776 b03f960 Thanks @edevil! - Add event-code support to temporary Worker deployments
Use wrangler deploy --temporary --event-code <code> to provision an account for an event. Wrangler requires explicit server acknowledgement before caching the account and keeps the event code out of its cache and telemetry.
#15817 6e77c53 Thanks @jamesopstad! - Allow framework commands to produce Preview Build Output with the experimental config
When cf previews deploy invokes a framework build command, Preview intent is now preserved. Function-based cloudflare.config.ts files receive isPreview: true, and generated Build Output is marked as a Preview build.
When Wrangler's --experimental-new-config flag or Vite's experimental.newConfig option is enabled, inferred configuration and runtime declarations are
#15778 cd7508c Thanks @jamesopstad! - Generate types during development and supported builds with Vite's experimental.newConfig option or Wrangler's --experimental-new-config flag (and --experimental-cf-build-output for builds)
When Wrangler's --experimental-new-config flag or Vite's experimental.newConfig option is enabled, inferred configuration and runtime declarations are now kept in .cloudflare/types/index.d.ts. Vite refreshes them during development and production builds. Wrangler refreshes them during development and when building with both --experimental-new-config and --experimental-cf-build-output. In the experimental wrangler.config.ts format, the types option is now top-level because it applies to both commands.
#15765 1bdb96d Thanks @th0m! - Prepare the required egress sidecar for local Containers without configured images
Wrangler dev and Vite dev/preview now pull the required sidecar for Durable Object-managed Containers that select their application image at start time. Previously, these Containers failed to start unless the sidecar image was already cached in Docker.
#15712 f5605f5 Thanks @alsuren! - Match D1 SQL statement splitting to the local SQLite runtime
Wrangler now uses SQLite's statement-completion state machine when splitting D1 SQL files. This keeps trigger, quoted identifier, comment, and keyword handling consistent with local execution.
This updates the bundled TOML parser that reads wrangler.toml to a version that addresses two advisories against 1.5.2: GHSA-7w5x-hrqm-74c2 (a value f
#15662 59267fc Thanks @oddharsh! - Update smol-toml to 1.8.0
This updates the bundled TOML parser that reads wrangler.toml to a version that addresses two advisories against 1.5.2: GHSA-7w5x-hrqm-74c2 (a value followed by a comment with no trailing newline, such as a=[1 #, put the parser in an infinite loop) and GHSA-v3rj-xjv7-4jmq (thousands of consecutive comment lines overflowed the stack). On the old version, wrangler deploy against a wrangler.toml ending in a=[1 # never returned; it now fails with Invalid TOML document: cannot find end of structure.
#15760 6906bf0 Thanks @yomna-shousha! - Warn when wrangler preview returns only non-custom-domain URLs even though custom-domain Preview URLs are configured.
#15761 354ebdb Thanks @podonnell-dev! - Fix Preview output artifacts to always include the resolved parent Worker name
Preview artifacts now use Wrangler's resolved Worker name instead of relying on the Preview API response to include it.
Updated dependencies []:
Runtime type headers without compatibility flags now end at the compatibility date, keeping generated types reproducible when tools remove trailing wh
#15762 ad20547 Thanks @podonnell-dev! - Fix wrangler types generating runtime headers with trailing whitespace
Runtime type headers without compatibility flags now end at the compatibility date, keeping generated types reproducible when tools remove trailing whitespace.
#15703 02c1d83 Thanks @KianNH! - Improve Container image listing and deletion
List all image pages using read-only credentials, validate tags before deletion, and report successful deletion when the garbage-collection request fails.
#15700 275184d Thanks @KianNH! - Fix Container SSH connection setup and shutdown
Prevent SSH connections from stalling during setup and ensure proxy processes exit when sessions close.
#15759 bd59eca Thanks @petebacondarwin! - Show valid sha256-prefixed tags in Container image listings
Container image listings now distinguish valid OCI tags such as sha256-release from synthetic digest entries such as sha256:<digest>.
Updated dependencies []:
Wrangler now displays placeholder replacement guidance directly beneath the suggested Preview configuration instead of as a separate warning. JSON out
#15744 0ed4c54 Thanks @podonnell-dev! - Improve wrangler preview onboarding guidance
Wrangler now displays placeholder replacement guidance directly beneath the suggested Preview configuration instead of as a separate warning. JSON output continues to include the guidance in its structured onboarding messages.
#15678 703922d Thanks @christhorwarth! - Read workers.dev URLs from the Worker resource during deployment
Wrangler no longer requires account-level subdomain permission to display Worker and version-preview URLs. It now uses the Worker-scoped URL fields while preserving account-level registration for accounts without a workers.dev subdomain.
Updated dependencies [14d946d]:
The root remains config.json , Worker configs are now worker.config.json , and Container configs are now container.config.json . Resource configs no l
#15713 3c75cad Thanks @jamesopstad! - Identify experimental Build Output resource configs by filename and location
The root remains config.json, Worker configs are now worker.config.json, and Container configs are now container.config.json. Resource configs no longer contain top-level type discriminators, while settings and build context are stored together in the root config.
#15713 3c75cad Thanks @jamesopstad! - Define experimental Cloudflare configuration with a single default export
Experimental cloudflare.config.ts files now define settings and resources together in a default-exported defineConfig() call. Add a Worker under worker, add Containers to the containers array, or omit both to provide settings only.
import * as entrypoint from "./src/index.ts" with { type: "cf-worker" };
export default defineConfig({
accountId: "...",
complianceRegion: "public",
worker: {
name: "my-worker",
compatibilityDate: "2026-09-18",
entrypoint,
},
});#15720 35668d7 Thanks @alexkli! - Add experimental --zone and --zone-id flags to wrangler deploy and wrangler triggers deploy to attach a zone to routes passed via --route
Routes passed on the command line were always sent to the Cloudflare API as bare patterns. Zones with an SSL for SaaS entitlement reject such routes with error 10082 ("When using wildcard host ssl for saas entitlement you must specify the zone per route using zone_id or zone_name"), and until now the only way to set a zone was in the config file, which --route overrides.
The new flags are experimental and must be enabled with --experimental-route-zones (alias --x-route-zones). Pass a single zone to apply it to all routes, or one zone per route in the same order as the --route flags:
wrangler deploy --x-route-zones --route "app.example.com/*" --route "api.example.com/*" --zone example.com
wrangler deploy --x-route-zones --route "a.example.com/*" --zone example.com --route "b.example.net/*" --zone example.net
--zone sets zone_name and --zone-id sets zone_id on each route. The two flags cannot be combined, and passing more than one zone requires exactly one per --route. Routes without zone flags behave exactly as before.
#15699 45b3b81 Thanks @skepticfx! - Remove the experimental Container image environment binding
Durable Object-managed Containers now use ctx.container.images without Wrangler generating env.EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES. Update code using the experimental environment binding to read ctx.container.images and regenerate your Worker types.
Version deployments identify managed applications from native named images, and --containers-rollout=none preserves native Container metadata. Containers without named images must first be provisioned with wrangler deploy; versions upload verifies that their applications already exist. The old binding is no longer read or reserved, including on previously uploaded versions. keep_vars retains existing variables as usual; redeploy without it to remove an existing experimental binding.
#15702 8235e6a Thanks @podonnell-dev! - Return structured configuration errors from wrangler preview --json
When a Worker is missing its Preview configuration, JSON mode now returns an error, a suggested_config patch, and any associated onboarding messages without interactive output or terminal formatting. This changes the private-beta Preview command to make automated onboarding reliable.
#15577 731a2ee Thanks @sdnts! - Add support for jurisdictions to Queues subcommands
#15711 91e2f86 Thanks @ghostwriternr! - Allow local Container images without exposed ports
Wrangler and the Cloudflare Vite plugin no longer reject images that omit Docker EXPOSE metadata. Local Containers can run command-only workloads or serve traffic through workerd without declaring an unused image port.
#15740 c5913a6 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260918.1 | ^5.20260921.1 |
| workerd | 1.20260918.1 | 1.20260921.1 |
#15471 0751490 Thanks @edmundhung! - Fix cf builds for static projects that serve assets from the project root
The experimental Build Output path now omits the reserved .cloudflare directory when the project root is used for static assets. This prevents recursive output copying in Wrangler while preserving the existing behaviour for other asset directories.
#15440 43b1f85 Thanks @HuzaifaAbdulRehman! - Rebase absolute non-JavaScript module specifiers when preserve_file_names is enabled
With preserve_file_names set, a non-JS module imported by an absolute path kept that path as its module name. The build machine's filesystem layout ended up inside the deployed Worker, and the module was never written to --outdir. A local dry run reported success while the upload failed server-side with error code 10021. Tooling that rewrites externals to absolute paths hits this, which is how it was found in @opennextjs/cloudflare with WASM imports.
Absolute specifiers are now rebased to ./<basename>, which is what the hashed branch of the same code already does minus the hash prefix. Relative specifiers keep the behaviour they had.
Wrangler and the Cloudflare Vite plugin now build Dockerfile-backed Container images when experimental Build Output is enabled. Container configs are
#15609 1f070c8 Thanks @emily-shen! - Build Containers when emitting experimental Build Output
Wrangler and the Cloudflare Vite plugin now build Dockerfile-backed Container images when experimental Build Output is enabled. Container configs are emitted under .cloudflare/output/v0/containers with local image references, while existing registry references pass through unchanged.
#15329 c4c9b75 Thanks @akshitsinha! - Evaluate Flagship flags locally during development
Flagship bindings now use the local Miniflare store by default in Wrangler and the Vite plugin, keeping development offline and isolated from production flags. Set remote: true on a binding to continue using its remote app.
Use wrangler flagship flags pull <APP_ID> to seed the store from a remote app. Flag management commands also accept --local to read and update the local store directly.
#15701 643e5cc Thanks @WillTaylorDev! - Pass Preview intent to defineWorker and upload its resolved configuration
Preview builds now evaluate programmatic Worker configuration with ctx.isPreview set to true and record that intent in Build Output. The shared Preview uploader deploys the resolved bindings and settings while preserving configured Preview base values when it creates a Preview.
#15705 a0485d5 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260917.1 | ^5.20260918.1 |
| workerd | 1.20260917.1 | 1.20260918.1 |
#15587 629ddef Thanks @Kuldeeep18! - Fix duration calculation for running workflow instances, steps, and attempts in wrangler workflows instances describe
wrangler workflows instances describe previously distorted the elapsed duration of in-progress instances, steps, and attempts across non-UTC timezones by stripping " GMT" from toUTCString(), causing new Date(...) to parse the timestamp in the local client timezone. The duration is now correctly computed against the current time.
Updated dependencies [a0485d5]:
Wrangler now validates and uploads the Issues setting alongside the existing logs and traces observability options. The experimental configuration for
#15684 6874aa9 Thanks @Ankcorn! - Add support for configuring real-time Issues with observability.issues.enabled
Wrangler now validates and uploads the Issues setting alongside the existing logs and traces observability options. The experimental configuration format supports the equivalent observability.issues.enabled option.
#15681 d96b319 Thanks @podonnell-dev! - Mark wrangler preview commands as open beta
Wrangler now labels Preview commands as open beta in help output and command warnings, matching the feature's public availability.
#15673 2b39fc2 Thanks @ghostwriternr! - Support explicit named Container image selection in Wrangler local development
Wrangler builds or pulls named images configured through Wrangler JSON or TOML and exposes their local tags through ctx.container.images. Pass one of those references to ctx.container.start({ image }) to select the image.
This extends the experimental Durable Object-managed Containers interface. Named images are opt-in and do not become the Container's default image. A Container without a default image must supply an image or full Container snapshot when starting.
#15689 876eea1 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260916.1 | ^5.20260917.1 |
| workerd | 1.20260916.1 | 1.20260917.1 |
You can now configure placement in the previews block. Preview-specific placement overrides the top-level placement configuration for Preview Defaults
#15600 bac0c6a Thanks @podonnell-dev! - Add placement configuration for Previews
You can now configure placement in the previews block. Preview-specific placement overrides the top-level placement configuration for Preview Defaults and deployments.
#15600 bac0c6a Thanks @podonnell-dev! - Improve onboarding guidance for Previews (when previews block is missing from configuration file)
When a local previews block is absent, Wrangler writes the Preview Base configuration to the local config file. When no Preview Base configuration exists, Wrangler prints a placeholder configuration derived from production bindings and warns against reusing production binding configuration.
#15483 71b6f10 Thanks @tpmmorris! - Align Local Explorer Workflow instance status requests with production
Local Explorer and Wrangler local mode now use the production-compatible status request field for pausing, resuming, restarting, and terminating Workflow instances. Direct Local Explorer API consumers must replace the previous action field with status.
Successful Local Explorer status updates now return the production-compatible instance status and response timestamp instead of the local-only result.success acknowledgement.
#15665 ad23e6e Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260915.1 | ^5.20260916.1 |
| workerd | 1.20260915.1 | 1.20260916.1 |
#15655 be2437a Thanks @WillTaylorDev! - Send exports with Worker Preview deployments
wrangler preview dropped the exports block from deployment requests. Durable Objects reached through ctx.exports had no Preview namespace, and cache settings for each entrypoint were lost too.
Command telemetry now records a coarse category for the entry-point/assets positional ( wrangler deploy <path> ) under sanitizedArgs.path , so we can
#14587 76c0ce6 Thanks @MattieTK! - Categorise the positional path argument to wrangler deploy and wrangler versions upload in command telemetry
Command telemetry now records a coarse category for the entry-point/assets positional (wrangler deploy <path>) under sanitizedArgs.path, so we can understand whether people pass a file, a directory, or a relational reference such as . or ../example. The possible values are file, directory, current-dir, parent-relative, and not-found, or null when no positional is provided. The raw path is never sent — only the category.
#15597 a83d7ac Thanks @skepticfx! - Configure application-wide logs for experimental Durable Object-managed Containers
Set containers[].observability.enabled or containers[].observability.logs.enabled when using scheduling_policy: "durable_object". Normal deployments create missing applications and update explicitly configured log settings without a Container rollout. Omitted settings preserve the application configuration; root Worker observability is not inherited for this policy.
Version uploads may initialize missing applications but preserve existing settings. Deploying or rolling back Worker versions also preserves existing application settings, and --containers-rollout=none skips their updates.
#15597 a83d7ac Thanks @skepticfx! - Support per-image build options for experimental Durable Object-managed Containers
Set build_context and build_vars alongside dockerfile in a Container's named images entries. Context paths resolve relative to the Wrangler configuration file and default to the Dockerfile's directory. Build variables are passed as Docker build arguments. Entries using the same Dockerfile with different contexts or variables are built separately.
{
"containers": [
{
"class_name": "Sandbox",
"scheduling_policy": "durable_object",
"images": {
"app": {
"dockerfile": "./docker/Dockerfile",
"build_context": ".",
"build_vars": { "APP_ENV": "production" }
}
}
}
]
}#15638 fa79b26 Thanks @G4brym! - Support AI Search bindings in Worker Previews
wrangler preview now accepts ai_search and ai_search_namespaces entries in the previews block and includes them in Preview deployment bindings. This lets Workers that use AI Search instance or namespace bindings attach existing resources to Preview deployments, including preview-specific instance or namespace names.
These bindings are non-inheritable: declare them explicitly under previews. They attach to existing AI Search resources; preview does not provision new isolated instances or namespaces.
#15256 16d1310 Thanks @theoephraim! - [private beta]: Add --secrets-file and --var flags to wrangler preview
Like wrangler deploy and wrangler versions upload, wrangler preview now accepts a --secrets-file flag pointing to a JSON or .env format file, and --var KEY:VALUE pairs that are injected into the Preview deployment as plain text variables. CLI vars override same-named vars from the previews section of your config file, and secrets from the file take precedence over both:
wrangler preview --secrets-file .env.preview --var API_URL:https://api.example.com
#15453 ca71205 Thanks @G4brym! - Remove the gated Web Search binding and Wrangler command
The unreleased search binding and its experimental command have been removed from Wrangler, Miniflare, and configuration APIs.
#15597 a83d7ac Thanks @skepticfx! - Allow experimental Durable Object-managed Containers to link by name through exports
Containers using scheduling_policy: "durable_object" can now specify name and link from exports.<Class>.container without repeating class_name. Deploy and version upload resolve that link for image preparation, Worker metadata, and Container application creation.
#14775 1be7b97 Thanks @dario-piotrowicz! - Sync Local Explorer endpoint lists across agent hints
The Local Explorer endpoint list is now consistent across the three places it appears: the AGENTS.md template in create-cloudflare, the runtime agent hint in wrangler dev, and the Vite plugin agent hint. All three now include the observability/clear endpoint, use the canonical /cdn-cgi/local/explorer path, and have cross-reference comments pointing to each other.
#15409 b149147 Thanks @tpmmorris! - Fix per-query overrides for wrangler ai-search search
--score-threshold, --max-num-results, --filter, and --reranking are now sent using the AI Search request schema, so the service applies them to searches instead of ignoring them.
#15633 7db596c Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260911.1 | ^5.20260915.1 |
| workerd | 1.20260911.1 | 1.20260915.1 |
#14906 a0856da Thanks @exKAZUu! - Surface the original error message, name and stack when the dev server reports an internal error
Previously wrangler dev could exit with an empty ✘ [ERROR] log that gave no indication of what went wrong (e.g. Network connection lost., see #14641). These errors now include their original message, name and stack, so the failure is actually diagnosable.
#15179 cb0955f Thanks @rioaguspermana! - Treat 502, 503, and 504 as gateway errors during asset upload retries
Pages and Workers asset uploads now retry more patiently when the Cloudflare API responds with a 502, 503 or 504 gateway error, reducing concurrency and waiting longer between attempts instead of failing the deploy quickly.
#15399 982b806 Thanks @tpmmorris! - Improve over-limit run_worker_first errors when duplicate rules are present
The error now reports distinct and duplicate-entry counts and lists duplicated rules, making it clear when removing redundant entries can bring the configuration within the limit.
Too many `run_worker_first` rules were provided; 105 rules provided (99 distinct, 6 duplicate entries) exceeds max of 100. Note: duplicate entries count towards the route limit. Ensure that no duplicate rules are present in your `run_worker_first` configuration.
The duplicated rules found are:
- "/rule/0"
- "/rule/1"
- "/rule/2"
- "/rule/3"
- "/rule/4"
...and 1 more duplicated rule.
#12369 ffabe74 Thanks @43081j! - Replace execa with tinyexec for running subprocesses, shrinking the bundled Wrangler output.
#15633 7db596c Thanks @dependabot! - Preserve service-worker middleware error propagation with spec-compliant event dispatch
Wrangler's synthetic service-worker events now propagate listener exceptions to middleware without changing the behavior of user-created EventTarget instances.
#15400 e03822a Thanks @james-elicx! - Reduce the size of Wrangler's published package
Exclude test-only, build-only, and obsolete template files from the npm package while retaining all runtime templates.
#15631 c4a6279 Thanks @petebacondarwin! - Restore static asset upload concurrency after gateway errors
Static asset uploads previously remained at concurrency one for the rest of the deployment after any 524 response, which could make large deployments exceed the upload session lifetime. Successful uploads now restore the session's original concurrency gradually while retaining gateway throttling. Requests that were already in flight when throttling began do not restore capacity, so a burst of stale successes cannot immediately undo backpressure.
Updated dependencies [7db596c, e35c4a1, d3565a5, ca71205, 1015cfb, 982b806, 641df47]:
Updated dependencies [ 8997652 ]:
8997652]:
Wrangler now explains that DNS and TLS certificate provisioning may continue after a deploy adds a custom domain or enables its Preview URLs. Stable r
#15592 945aaa3 Thanks @WillTaylorDev! - Add a provisioning delay note when custom domain Preview URLs change
Wrangler now explains that DNS and TLS certificate provisioning may continue after a deploy adds a custom domain or enables its Preview URLs. Stable redeploys don't repeat the note.
This assumes that a request which matches the stored custom domain state doesn't restart provisioning. The client infers this from the API changeset and current domain record because this repository can't verify the backend behavior.
#15592 945aaa3 Thanks @WillTaylorDev! - Clarify production status labels for custom domain routes
Wrangler now prefixes explicit custom domain production states with production: so they match Preview labels. The updated labels appear in deployed trigger output and WRANGLER_OUTPUT_FILE_PATH.
#15602 47d906f Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260910.1 | ^5.20260911.1 |
| workerd | 1.20260910.1 | 1.20260911.1 |
#15592 945aaa3 Thanks @WillTaylorDev! - Avoid replacement prompts for custom domains already on the Worker
Wrangler now updates Preview settings without asking to replace a custom domain when that domain already belongs to the deployed Worker. It still asks before replacing domains attached to another Worker.
#15592 945aaa3 Thanks @WillTaylorDev! - Explain how to enable Preview URLs when a Preview deployment has none
wrangler preview now shows URL shapes and configuration snippets for Workers.dev and custom domains. The custom domain snippet preserves every configured route, and the guidance distinguishes missing settings from disabled ones.
This changes a private beta feature. The warning also makes clear that wrangler deploy publishes code from the current checkout.
shell-quote@1.8.1 is affected by a ReDoS in parse() ( CVE-2026-13311 / GHSA-395f-4hp3-45gv — an unauthenticated attacker who can feed a string into pa…
#15480 36aed7f Thanks @skepticfx! - Add Durable Object-managed Containers to top-level container configuration
Wrangler now accepts scheduling_policy: "durable_object" in the top-level containers array and creates its namespace-backed application after the Worker upload resolves the Durable Object namespace ID. The namespace ID is also the application ID, so repeated deploys idempotently ensure the same application without name-based lookup, modification, or a Containers rollout.
Durable Object-managed entries accept class_name, scheduling_policy, an optional name, and an optional named images map. Scheduler-only fields are rejected. Each image provides either a local dockerfile or a digest-pinned managed-registry image. Wrangler builds or resolves each image, waits while Cloudflare prepares it for the Containers runtime, and uploads the resulting references with the Worker version for access through ctx.container.images and env.EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES. Local development support for these entries is deferred to a follow-up.
Existing scheduler-backed entries and Durable Object migrations continue to work unchanged.
With --containers-rollout=none, existing Workers retain their deployed Container metadata and image binding even when local containers is omitted or empty; local scheduler edits are also ignored. The upload stops if the deployed versions cannot be recovered. Existing Workers for Platforms dispatch scripts reject this flag before upload because their API does not expose enough metadata to preserve Container associations safely. First deployments can still skip Container preparation and rollout. Without this flag, removing managed Containers, including by omitting containers entirely, clears the experimental image binding even with keep_vars.
versions deploy validates the selected versions before changing traffic and creates their Durable Object-managed applications only after deployment succeeds. Both deploy and versions deploy report partial completion if application creation fails afterward, with instructions to retry the same command.
EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES is a temporary, reserved Wrangler binding until native Container image metadata is available. Its class keys identify managed applications during versions deploy, including classes with empty image maps. User configuration cannot declare a binding with this name; existing versions that already use it are treated as Container configuration.
#15493 493e635 Thanks @GregBrimble! - Remove wrangler preview settings commands
The private-beta wrangler preview settings and wrangler preview settings update commands are no longer available.
#15411 0b43395 Thanks @xgame92! - Fail wrangler versions upload early when a Worker has a pending Durable Object migration
Wrangler now directs users to run wrangler deploy to apply the migration instead of sending a version upload request that the API will reject.
#15518 9d75006 Thanks @taylorlee! - Detect named-only module Worker entrypoints correctly
Wrangler now distinguishes named-only module Workers from legacy Service Workers that happen to have named exports. A default export identifies a module Worker; otherwise, legacy addEventListener registration identifies Service Worker format.
#15581 b605aa6 Thanks @MattieTK! - Correct Pages-to-Workers delegation analytics for forced and ineligible commands
The legacy forced result counted every agent-driven Pages command using --force, including commands that could never have been delegated. Wrangler now emits eligible_forced only when --force prevents an otherwise eligible delegation, and records other agent commands as ineligible with a bounded reason and whether force was used.
#15432 f45b596 Thanks @razethion! - Prevent delayed internal errors from fetch-only remote bindings
Fetch-only remote bindings such as D1 and R2 previously opened an unused WebSocket RPC session. RPC sessions are now created only when an RPC method is called.
#15585 f69f95a Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260908.1 | ^5.20260910.1 |
| workerd | 1.20260908.1 | 1.20260910.1 |
#15554 bff525d Thanks @XiaoZ-0218! - Add the missing transferred_classes migration to the config schema
DurableObjectMigration described new_classes, new_sqlite_classes, renamed_classes and deleted_classes, but not transferred_classes. normalizeAndValidateConfig has always validated that key, and the deploy path forwards it to the API along with the rest of the step, so Transfer migrations worked — but config-schema.json is generated from the type, so an editor resolving $schema reported a valid, documented migration as an unknown key.
Adding the field to the type puts it in the generated schema. No runtime change.
#15584 96688b3 Thanks @Svector-anu! - Bump shell-quote to 1.9.0+ to pick up two disclosed advisories
shell-quote@1.8.1 is affected by a ReDoS in parse() (CVE-2026-13311 / GHSA-395f-4hp3-45gv — an unauthenticated attacker who can feed a string into parse() can block the event loop for tens of seconds with plain space-separated input, no shell metacharacters required) and by an object-token escaping bug in quote() (CVE-2026-9277 / GHSA-w7jw-789q-3m8p), both fixed upstream in 1.9.0. Wrangler's parse() wrapper (src/utils/shell-quote.ts) is reachable from pages dev/init command-line parsing, so the ReDoS applies; the quote() call site only ever passes string arguments, so the object-token issue was not reachable here, but there is no reason to stay on a vulnerable range once a patch exists.
#15563 ed5797a Thanks @Bortlesboat! - Encode filenames in Pages HTML redirects
Fix wrangler pages dev returning a 502 response when redirecting HTML paths containing Unicode characters. Keep reserved characters in filenames encoded in the redirect destination and preserve the request query string.
#14889 128235a Thanks @chinesepowered! - Fix wrangler types --strict-vars=false emitting invalid TypeScript for an empty array var
A var whose value was an empty array produced ()[], which is a syntax error. Because this lands in the generated worker-configuration.d.ts, it did not just break that one line — the whole file failed to parse, so no binding types resolved at all. An empty array now generates unknown[].
#15494 f8aea7e Thanks @GregBrimble! - Use previews_base_config for Preview configuration
Preview commands now read the Worker Previews Base configuration from the previews_base_config API field.
#15569 24ef86b Thanks @RealBhupesh! - Fix wrangler workflows instances describe crashing on dynamic retry delays
The Workflows API serializes function retry delays as "[dynamic]". The describe command previously parsed that as a duration, produced an Invalid Date, and threw RangeError: Invalid time value before printing remaining steps. It now renders unknown (dynamic delay) and also tolerates attempts whose end timestamp is missing.
Updated dependencies [f45b596, f69f95a, a549e58, dbb3ff4, fea3cd0, 6bd7b6c, 15cd6e1, be1caec, dbc9506]:
Wrangler now accepts container-specific observability settings via containers[].observability , including application-level targeting fields for Conta
#14372 dbf6aad Thanks @ichernetsky-cf! - Add containers[].observability support to wrangler deploy
Wrangler now accepts container-specific observability settings via containers[].observability, including application-level targeting fields for Containers. Root observability continues to work as a fallback when a container does not define its own observability settings.
wrangler deploy now preserves legacy configuration.observability for existing container apps that still use rollout-based observability, while using top-level application observability for new or already-migrated apps.
Existing application diffs are now normalized even when stored resource limits cannot be mapped to a named instance type. API-only metadata and equivalent managed-registry image names no longer appear as edits or affect whether deployment changes require a rollout.
#15004 e20df20 Thanks @MattieTK! - Delegate agent Pages project creation with a production branch to Workers
When run by an AI agent, wrangler pages project create --production-branch <name> is now eligible for delegation to a Workers static-assets deploy. The production branch names the target that a Workers deploy would publish to, so it does not need to disqualify a brand-new project from delegation.
wrangler pages deploy --branch <name> remains on Pages because an interactive new-project flow separately prompts for its production branch. The deployment branch may therefore represent a preview and cannot safely be converted into a production Workers deployment.
#15004 e20df20 Thanks @MattieTK! - Widen agent Pages-to-Workers delegation to new projects on accounts that already use Pages
When run by an AI agent, wrangler pages deploy and wrangler pages project create now delegate a brand-new static Pages project to a Workers static-assets deploy even when the account already has other Pages projects. The gate is now per-project rather than per-account: a command targeting a project that already exists stays on Pages, but a new project is delegated regardless of the account's other Pages projects.
A project name restored from the Pages configuration cache is only used when the cache belongs to the currently authenticated account. An account-matching cached name remains on Pages even when the project is missing remotely, preserving the user's recorded Pages intent. After switching accounts, an otherwise unnamed deploy stays on Pages rather than treating a stale cached project name as a new project on the selected account.
#15560 edb3631 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260907.1 | ^5.20260908.1 |
| workerd | 1.20260907.1 | 1.20260908.1 |
#15557 63c7ff1 Thanks @tomekancu! - Fix wrangler d1 execute --local being extremely slow with large SQL files or commands
The local SQL splitter consumed quoted strings and comments character-by-character, re-checking the full accumulated string each time. This made splitting a large quoted value or comment quadratic, so seed files could take tens of seconds to run. The splitter now only inspects a bounded trailing window on each step, making splitting effectively linear. The remote path is unaffected as it imports the file server-side.
#15542 a4e41df Thanks @NAVEENKUMARKR777! - Fix wrangler dev running the custom build command twice on startup and on every config change
Wrangler already runs the custom build.command once before starting wrangler dev, to resolve the Worker's entry point. When dev.watch wasn't explicitly disabled, BundlerController then unconditionally ran the same build command again the moment it started watching for changes, and repeated this on every subsequent config reload too.
For fast build commands this just meant duplicate log output (e.g. a vite build visibly running twice at startup). For slower or stateful build commands, running two builds concurrently against the same output files could corrupt the result or fail outright (for example, non-deterministic wasm-opt failures have been reported for Rust builds).
The initial watcher setup now only bundles the output the build command already produced, instead of re-running the command. Real file changes detected by the watcher still re-run the build command as before.
The following dependency versions have been updated:
#15502 8bbcb9f Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260903.1 | ^5.20260904.1 |
| workerd | 1.20260903.1 | 1.20260904.1 |
#15543 2b42d6f Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260904.1 | ^5.20260907.1 |
| workerd | 1.20260904.1 | 1.20260907.1 |
#15323 ea5634e Thanks @Sakshamm-Goyal! - Prevent Wrangler from exiting when a process capturing its output closes the pipe.
Wrangler now ignores broken-pipe errors from stdout and stderr while preserving the existing failure behavior for other output errors.
#14001 c0c6504 Thanks @for-the-kidz! - Update bundle size warning thresholds to use uncompressed size instead of gzip size
The compressed script size limits (3 MiB free / 10 MiB paid) have been removed server-side in favor of a single 64 MiB uncompressed limit. The bundle size reporter now compares the uncompressed bundle size against this 64 MiB limit for its color-coded warnings, instead of comparing gzip size against the old 3 MiB compressed limit.
#15499 ffc7efd Thanks @WillTaylorDev! - Honor Workers Builds name overrides in wrangler preview
Preview commands now target the Worker name supplied by Workers Builds instead of the name in local Wrangler configuration. This prevents preview builds from failing when the two names differ.
#15252 682cd44 Thanks @GregoryCollett! - wrangler dev no longer exits when a request to your Worker fails transiently
Previously, a transient network failure on a single request — most commonly a request arriving just as an idle internal connection was closed, after roughly five seconds without traffic — could take down the whole dev server with an empty ✘ [ERROR], leaving the port unbound until restarted. In CI test suites, one such failure caused every remaining test to fail with connection errors.
wrangler dev now automatically retries the affected request if it is safe to repeat (GET and HEAD requests). If a request still fails, it fails individually — the error is logged with the request method and URL — and the dev server keeps serving.
Updated dependencies [8bbcb9f, 2b42d6f]:
Pipelines is in open beta. wrangler pipelines sinks create and the interactive setup flow now pass the selected JSON compression to the Pipelines API.
#15460 93d72a5 Thanks @QnJ1c2kNCg! - Support gzip compression for JSON Pipelines sinks
Pipelines is in open beta. wrangler pipelines sinks create and the interactive setup flow now pass the selected JSON compression to the Pipelines API. JSON sinks accept uncompressed or gzip, while Parquet retains its existing compression options and zstd default.
#15358 d2d8eea Thanks @pombosilva! - Add a --json flag to the wrangler workflows commands
Every wrangler workflows command now accepts --json, which emits the raw API payload instead of the human-readable rendering. The formatted output remains the default, so existing usage is unaffected:
wrangler workflows instances list my-workflow --json
The JSON output carries raw values rather than a serialisation of the formatted view: ISO timestamps instead of locale-formatted dates, plain status strings instead of emojified labels, and no presentation-only derived fields.
#15469 d40a634 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260831.1 | ^5.20260902.1 |
| workerd | 1.20260831.1 | 1.20260902.1 |
#15481 7c1b2a6 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260902.1 | ^5.20260903.1 |
| workerd | 1.20260902.1 | 1.20260903.1 |
#15472 f6fb347 Thanks @emily-shen! - Tolerate missing permissions during wrangler delete cleanup checks
wrangler delete now warns and continues when it cannot inspect Worker dependencies or clean up legacy Workers Sites KV namespaces because of missing permissions. The Worker delete request itself still fails normally if the token cannot delete the Worker.
#15472 f6fb347 Thanks @emily-shen! - Tolerate missing resource permissions during resource provisioning
When Wrangler cannot check whether a bound resource exists because the API returns a 403, it now skips automatic provisioning for that resource type and continues the deploy. The deploy may still fail later if the resource is missing.
#15476 dc24057 Thanks @christhorwarth! - Fix remote development with static assets for API tokens using granular Worker permissions
Wrangler now creates Workers.dev preview sessions through the Worker-scoped endpoint and derives the preview hostname from the session response. This avoids requiring account-level Workers subdomain access.
Binding conversion, printing, and local-development validation are now exported from @cloudflare/workers-utils so they can be shared by Wrangler, the
#15454 dbbb795 Thanks @jamesopstad! - Move binding utilities into @cloudflare/workers-utils
Binding conversion, printing, and local-development validation are now exported from @cloudflare/workers-utils so they can be shared by Wrangler, the Cloudflare Vite plugin, and other consumers.
The corresponding exports have been removed from @cloudflare/deploy-helpers. Consumers should import them directly from @cloudflare/workers-utils instead.
Wrangler's unstable_printBindings API now accepts the bindings and an options object instead of five positional parameters.
#15353 87a7acf Thanks @pombosilva! - Add --date-start and --date-end filters to wrangler workflows instances list
You can now narrow an instance listing to a creation-time window:
wrangler workflows instances list my-workflow --date-start 2026-01-01 --date-end 2026-01-31
Either flag can be used independently. Both accept an ISO 8601 date or timestamp and are normalised to UTC before being sent, so a date-only value such as 2026-01-01 works as well as a full 2026-01-01T13:00:00Z. The bounds are inclusive and compose with the existing --status filter.
#15379 ea28cc3 Thanks @ibbykhazanchi! - Add query string redaction to Workers observability configuration
Set observability.redact_query_string in wrangler.json or observability.redactQueryString in the experimental cloudflare.config.ts format to remove query strings from request URLs in logs and traces.
#14915 707cb6f Thanks @longlho! - Include exact raw and gzip-compressed Worker bundle sizes in structured deploy and version-upload output.
#15436 200780f Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260828.1 | ^5.20260831.1 |
| workerd | 1.20260828.1 | 1.20260831.1 |
#15406 b3f2628 Thanks @james-elicx! - Reduce the installed bundle sizes of Wrangler and Miniflare
Wrangler now resolves bundled workspace dependencies from source during monorepo builds so unused exports can be removed. Miniflare, its shared CLI and container dependencies now use granular @cloudflare/workers-utils entry points instead of loading the package barrel, reducing the raw Wrangler and Miniflare artifacts by 6.16 MiB (31.4%) and 1.06 MiB (22.9%) respectively without changing runtime behavior or installed dependencies.
#15398 1809c5e Thanks @james-elicx! - Reduce Wrangler's published package size
Stop including the unused build metafile in the npm package, reducing its unpacked size by approximately 3.1 MiB.
#15382 b3fb2bf Thanks @Om-singhaI! - Skip the skills install status lookup when telemetry is disabled
Telemetry events include a currentAgentSkillsInstalled property, and computing it can query the GitHub API. The lookup used to start before the telemetry permission was checked, so users who opted out via WRANGLER_SEND_METRICS, DO_NOT_TRACK, or send_metrics in their Wrangler config still triggered network requests on behalf of telemetry. The dispatcher now checks the permission first and only performs the lookup when telemetry is enabled.
The following dependency versions have been updated:
#15383 eb01850 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260826.1 | ^5.20260827.1 |
| workerd | 1.20260826.1 | 1.20260827.1 |
#15393 e1df91a Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260827.1 | ^5.20260828.1 |
| workerd | 1.20260827.1 | 1.20260828.1 |
Updated dependencies [eb01850, e1df91a, b23de74, 015550a, 015550a, 015550a, 3650d29, b23de74]:
The limit is the maximum number of Workflow instances that can run concurrently. It is validated as a positive integer and persisted on deploy; the ce
#15356 fe265f8 Thanks @rubuy-74! - Add support for configuring a per-workflow max concurrency limit via workflows[].concurrency.limit in your Wrangler config.
The limit is the maximum number of Workflow instances that can run concurrently. It is validated as a positive integer and persisted on deploy; the ceiling is enforced server-side. Concurrency is ignored in local development.
{
"workflows": [
{
"binding": "MY_WORKFLOW",
"name": "my-workflow",
"class_name": "MyWorkflow",
"concurrency": { "limit": 10 }
}
]
}
#15367 412c79e Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260825.1 | ^5.20260826.1 |
| workerd | 1.20260825.1 | 1.20260826.1 |
#15375 92874f6 Thanks @WillTaylorDev! - Upload wrangler preview modules as multipart form data
wrangler preview used to base64 the bundle, its modules, and any sourcemaps into a single JSON request body. Base64 inflates content by a third, so a Worker with a large sourcemap could exceed the API request size limit and fail to deploy.
The preview deployment request is now multipart/form-data. The deployment settings travel in a metadata part and each module follows as its own part carrying raw bytes, matching how wrangler deploy already uploads a Worker.
Updated dependencies [412c79e]:
Workflow instances are retained for an account-wide default period after they finish. You can now set a per-Workflow default in your Wrangler configur
#15332 d1cc3af Thanks @pombosilva! - Add default_retention to Workflow bindings for configuring how long instances are retained
Workflow instances are retained for an account-wide default period after they finish. You can now set a per-Workflow default in your Wrangler configuration, applied to instances that do not specify their own retention:
{
"workflows": [
{
"binding": "MY_WORKFLOW",
"name": "my-workflow",
"class_name": "MyWorkflow",
"default_retention": {
"success_retention": "3 days",
"error_retention": "7 days"
}
}
]
}Each side is optional and accepts either a duration string such as "3 days" or a whole number of milliseconds. Durations are interpreted by the Workflows API, which also caps them at your account's retention limit.
#15064 693ca29 Thanks @tpmmorris! - Include a chronological list of handler events in email test harness results, so programmatic local email tests can assert the order in which messages are received, forwarded, replied to, or rejected.
const result = await server.getWorker().email({
from: "sender@example.com",
to: "inbox@example.com",
raw: [
"From: Sender <sender@example.com>",
"To: Inbox <inbox@example.com>",
"Message-ID: <test@example.com>",
"Subject: Test email",
"",
"Hello from the test harness",
].join("\r\n"),
});
expect(result.events).toEqual([
{ type: "received", timestamp: expect.any(String) },
{
type: "forward",
timestamp: expect.any(String),
messageId: expect.any(String),
},
{
type: "reply",
timestamp: expect.any(String),
messageId: expect.any(String),
},
]);#15065 ad89456 Thanks @mtlemilio! - Add experimental wrangler hyperdrive planetscale signature for provisioning Cloudflare-billed PlanetScale databases
wrangler hyperdrive planetscale signature prints a signed authorization as JSON, proving to PlanetScale that Cloudflare will be billed for the database you are about to create:
npx wrangler hyperdrive planetscale signature | \
pscale database create <name> \
--org <org> \
--engine postgresql \
--cloudflare-billing @- \
--format jsonpscale database create defaults to Vitess, so pass --engine postgresql for a Postgres database, and --format json is recommended when the output is consumed by an agent.
This requires pscale v0.313.0 or newer. Wrangler authorizes the Cloudflare billing side only, so your PlanetScale credentials stay between you and pscale.
The signature is a cryptographically signed token that authorizes creating a database billed to your Cloudflare account. Treat it as a credential and do not share it. Piping it, as above, is recommended over passing it as a command line argument.
This command is experimental and its interface may change.
#15134 c66d2d5 Thanks @gpanders! - Enable FUSE-capable local container development
Miniflare now automatically passes the Docker privileges needed for FUSE to local Durable Object containers when using local rootless Docker on Linux with /dev/fuse available, or a local Docker engine on macOS or through WSL where Linux containers run in a VM. This applies to Wrangler, the Cloudflare Vite plugin, and direct Miniflare use.
#15326 9fcb1c9 Thanks @jamesopstad! - Record the selected mode in the Build Output Specification top-level config.json
The mode a build was produced in is now written to .cloudflare/output/v0/config.json as a mode field, alongside the account and compliance settings.
#14966 a4c3458 Thanks @yomna-shousha! - Add pull request metadata to wrangler preview deployments
wrangler preview now detects the pull request associated with the current CI run (GitHub Actions, GitLab CI, CircleCI, and a generic PULL_REQUEST_URL/PR_URL/CHANGE_URL fallback) and attaches it, along with the repository URL, to the preview deployment as annotations (workers/pull_request_number, workers/pull_request_url, workers/repository_url).
This is best effort: if no pull request can be detected, nothing changes. When a pull request is detected, its URL is now also shown in the wrangler preview command output.
#15307 433fa98 Thanks @for-the-kidz! - Add pull request title to wrangler preview deployment annotations
wrangler preview now also detects the title of the pull/merge request associated with the current CI run (GitHub Actions and GitLab CI, plus a generic PULL_REQUEST_TITLE fallback) and attaches it to the preview deployment as the workers/pull_request_title annotation, alongside the existing pull request number/URL, repository URL, and commit SHA annotations.
This is best effort: if no pull request title can be detected, nothing changes.
#15294 4a67a28 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260820.1 | ^5.20260821.1 |
| workerd | 1.20260820.1 | 1.20260821.1 |
#15328 2d78137 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260821.1 | ^5.20260823.1 |
| workerd | 1.20260821.1 | 1.20260824.1 |
#15346 04e8564 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260823.1 | ^5.20260825.1 |
| workerd | 1.20260824.1 | 1.20260825.1 |
#15246 daefb3c Thanks @edmundhung! - Prepare autoconfig for multiple configuration targets
Add target-specific configuration output and command detection while preserving Wrangler's existing setup and deployment behavior.
#15320 c809851 Thanks @Om-singhaI! - Fix wrangler login --use-keyring incorrectly reporting that secret-tool is missing on Linux
Libsecret's secret-tool does not support --version; it prints usage and exits 2, which Wrangler previously interpreted as unavailable. Wrangler now reports it missing only when launching the executable fails.
#15336 22182da Thanks @podonnell-dev! - [private beta]: Explain unavailable Preview URLs after wrangler preview deployments
When a Preview deployment has no active URLs, Wrangler now explains how to enable Preview Deployments on workers.dev or a custom domain.
#15296 d589d30 Thanks @MattieTK! - Stop automatically offering to install Cloudflare skills for new users
Wrangler will no longer prompt new users to install Cloudflare skills after commands complete. It will continue to offer updates to skills that Wrangler previously installed.
Updated dependencies [aa54b49, 4a67a28, 2d78137, 04e8564, 693ca29, 693ca29, 693ca29, 37ed753, f76b68e, c66d2d5, 693ca29, 74de3ab, 0cb8690, dd5148d, 82d11fc]:
You can now configure a Worker to receive raw socket connections during wrangler dev , delivered directly to the Worker's connect(socket, env, ctx) ha
#14995 59872c4 Thanks @ThomasRubini! - Add connect trigger for raw sockets
You can now configure a Worker to receive raw socket connections during wrangler dev, delivered directly to the Worker's connect(socket, env, ctx) handler:
{
"connect": [{ "protocol": "tcp", "port": 5432 }]
}Each entry opens a listening socket on 127.0.0.1 (or the given address) that forwards incoming connections straight to the Worker, bypassing the local dev HTTP entry point. This requires the experimental compatibility flag. Only "tcp" is supported at the moment.
@cloudflare/config also supports declaring this trigger via triggers.connect(...), which lowers to the connect field above:
import { defineWorker, triggers } from "@cloudflare/config";
export default defineWorker({
triggers: [
triggers.connect({ protocol: "tcp", port: 5432, address: "127.0.0.1" }),
],
});#15172 c68f9cb Thanks @WillTaylorDev! - Add container support to worker previews
Worker previews now support containers through a new previews.containers configuration block. Container configuration doesn't inherit, so declare containers explicitly in the previews block to enable them for previews. This mirrors how previews.durable_objects works today. Wrangler names each preview container application {worker_name}_{preview_slug}_{class_name}, normalising and shortening the result to what the API accepts. Either change appends a short digest of the composed name, so two names that would otherwise land on one stay distinct. An entry cannot set its own name, because application names are unique to an account and a fixed name would collide between two previews of the same Worker. A Durable Object class is backed by at most one container application, so the validator rejects two entries that share a class_name. Wrangler skips container applications bound to Durable Object classes that another Worker implements through script_name, because the implementing Worker owns its own container application. A binding is not required: a Durable Object declared through migrations or exports and reached only over ctx.exports can still back a container. Every entry must set class_name. A previews.containers entry whose class_name matches no Durable Object class at all is rejected before the preview deployment is created, so a typo fails loudly instead of producing a preview with no container.
Wrangler creates the container applications on wrangler preview. Deleting a preview tears them down server side, so wrangler preview delete doesn't remove them.
Container build and deploy progress prints to stdout. wrangler preview --json suppresses wrangler's own output so it doesn't interleave with the payload, and warnings and errors still go to stderr. Docker's build output and the progress spinner write to stdout directly and bypass that suppression, so parse --json from a non interactive shell, where the spinner is skipped, and prefer a prebuilt image over a Dockerfile.
#15174 649f667 Thanks @WillTaylorDev! - [private beta]: Create the parent Worker automatically when wrangler preview targets one that doesn't exist yet
Previews hang off a parent Worker, so running wrangler preview before the Worker had ever been deployed failed with a raw API error naming the Preview endpoint. Wrangler now offers to create an empty parent Worker and then carries on creating the Preview. The parent uses the same workers.dev and Preview URL settings that wrangler deploy would resolve, without applying routes or cron triggers. In non-interactive environments, Wrangler creates the Worker without asking.
#14735 30c2d47 Thanks @vaishnav-mk! - Add individual and batch Workflow instance deletion to the runtime and SDK.
WorkflowInstance.delete() deletes one instance. Self-deletion stops the current execution.env.MY_WORKFLOW.deleteBatch(instanceIds) deletes up to 100 instances and returns { deleted, errors } per input position.wrangler workflows instances delete <name> [id..] deletes instances remotely or with --local; IDs can also come from a JSON array passed with --filename, with a combined limit of 100.#15260 5ae9d5b Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260815.1 | ^5.20260816.1 |
| workerd | 1.20260815.1 | 1.20260816.1 |
#15264 4b52975 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260816.1 | ^5.20260819.1 |
| workerd | 1.20260816.1 | 1.20260819.1 |
#15277 ce9b151 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @cloudflare/workers-types | ^5.20260819.1 | ^5.20260820.1 |
| workerd | 1.20260819.1 | 1.20260820.1 |
#15192 ef73a28 Thanks @ondraulehla! - Fixes kv bulk put corrupting binary values written to local KV
Values marked base64: true were stored incorrectly whenever they contained bytes that do not form valid UTF-8, which covers images, compressed data and most other binary payloads. A Worker reading such a key back under wrangler dev got a different, longer value than the one that was written: a 12 byte PNG header came back as 20 bytes.
kv bulk put writes to local KV by default, so the plain command was the affected one. Remote writes were never affected, and neither were entries without base64 or values written with kv key put.
#15284 39dcea6 Thanks @emily-shen! - Move deploy output writing into shared deploy helpers
#15130 99a1f49 Thanks @emily-shen! - Remove unsupported remote configuration from Workflow bindings
Workflow bindings no longer accept remote in configuration, as remote Workflow bindings have never actually been supported.
#15278 f2437e6 Thanks @Sosokker! - Fix the --temporary error on commands that authenticate more than one time
wrangler d1 migrations apply --remote --temporary failed with this error: You're already authenticated with Cloudflare, so --temporary can't be used. The failure occurred with no login and with no CLOUDFLARE_API_TOKEN. This command authenticates one time for each statement that it runs. The first authentication makes a temporary preview account. The second authentication read the token of this new account as an earlier login.
Wrangler now uses again the temporary account from the same command run. Commands that authenticate more than one time now work as wrangler deploy --temporary works. If real credentials are available, --temporary is still an error.
Updated dependencies [59872c4, 99a1f49, 5ae9d5b, 4b52975, ce9b151, 99a1f49, 99a1f49, 30c2d47]:
One column per quarter.
{ "images": { "url_transformations": { "enabled": true, "allowed_origins": ["images.example.com"] } } }