Repository navigation
Releases
wrangler@4.166.0
Minor Changes
-
#16961
bf7568aThanks @dario-piotrowicz! - Show configured trigger targets during experimentalwrangler triggers deploy --dry-runDry 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
be6aa81Thanks @mglewis! - Addimages.url_transformationsto the Wrangler configurationThe
imagesblock now accepts aurl_transformationsobject for controlling/cdn-cgi/image/transformations on requests served by a Worker.enabledis required, andallowed_originsoptionally lists the origins images may be fetched from (use["*"]to allow any origin).bindingis now optional, sourl_transformationscan be configured without an Images binding:Like the rest of the
imagesblock,url_transformationsis not inherited by named environments, and must be specified in each environment that needs it.cloudflare.config.tsgains the equivalent setting as a top-levelimagesfield on the Worker, with the Images binding remaining inenv:export default defineConfig({ worker: { name: "my-worker", compatibilityDate: "2026-11-01", images: { urlTransformations: { enabled: true, allowedOrigins: ["images.example.com"], }, }, }, });
cf migratecarriesimages.url_transformationsover to this field.This change adds configuration and validation only.
url_transformationsis not supported inpreviews. -
#14114
dce615cThanks @dario-piotrowicz! - Add--show-diffflag towrangler triggers deployWhen
--show-diffis 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 theworkers_dev/preview_urlssubdomain 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-runto preview these changes without actually deploying. Displaying a diff requires authentication, including during a dry run.
Patch Changes
-
#17031
95fd4c2Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-19Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
-
#17031
95fd4c2Thanks @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
bf7568aThanks @dario-piotrowicz! - Validate external Workflow settings before updating Worker triggersReject
limits,concurrency,schedules,default_retention, andjurisdictionconfigured 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
56974d4Thanks @petebacondarwin! - Warn when invocation logs are enabled while logs are disabledConfiguration validation now warns when
observability.logs.invocation_logsistrueandobservability.logs.enabledisfalse. Invocation logging remains disabled untilobservability.logs.enabledis set totrue. -
#17072
3c91a13Thanks @mykcs! - Recover when concurrentwrangler previewbuilds 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
08eeaf4Thanks @Naapperas! - Wait for a just-uploaded Worker version to become readable during deploysFor a few seconds after a version is uploaded, the Workers API can alternate between returning it and reporting it as not found.
wrangler versions deployfailed on the first not-found read, andwrangler deployfor 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
f3f7bbcThanks @cpojer! - Stop running Docker at the end of builds for projects with no ContainersBuilds that write the Build Output Specification ran
docker image lson 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
4f5b118Thanks @petebacondarwin! - Update Undici to 7.30.2 to include upstream security fixesThis 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
1b563dbThanks @petebacondarwin! - Fix remote bindings authentication with API tokens scoped to an individual WorkerRemote 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
getPlatformProxyand 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](https://github.com/cloudflare/workers-sdk/commit/629f135e425...
create-cloudflare@2.75.0
Minor Changes
-
#17074
4717798Thanks @petebacondarwin! - Scaffold SvelteKit projects for Workers onlyThe SvelteKit Cloudflare adapter no longer supports Pages. Use
--framework svelte --platform workersto create a new project, or omit--platformto select Workers automatically. The adapter now sets the Worker entry point and assets directory at build time. Existing projects are not modified.
Patch Changes
-
#17041
2469829Thanks @camc314! - Usebundlermodule resolution in the remaining TypeScript Worker templatesThe common, Durable Object, Workflows, Queues, and Scheduled TypeScript templates used
moduleResolution: "node", which TypeScript 6 deprecates. New projects created from these templates now usebundlerresolution, matching the other Worker templates and the way Wrangler bundles Worker code. -
#17031
95fd4c2Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-19Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
-
#17043
4f5b118Thanks @petebacondarwin! - Update Undici to 7.30.2 to include upstream security fixesThis 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.
@cloudflare/workers-utils@0.56.0
Minor Changes
-
#16679
be6aa81Thanks @mglewis! - Addimages.url_transformationsto the Wrangler configurationThe
imagesblock now accepts aurl_transformationsobject for controlling/cdn-cgi/image/transformations on requests served by a Worker.enabledis required, andallowed_originsoptionally lists the origins images may be fetched from (use["*"]to allow any origin).bindingis now optional, sourl_transformationscan be configured without an Images binding:{ "images": { "url_transformations": { "enabled": true, "allowed_origins": ["images.example.com"] } } }Like the rest of the
imagesblock,url_transformationsis not inherited by named environments, and must be specified in each environment that needs it.cloudflare.config.tsgains the equivalent setting as a top-levelimagesfield on the Worker, with the Images binding remaining inenv:export default defineConfig({ worker: { name: "my-worker", compatibilityDate: "2026-11-01", images: { urlTransformations: { enabled: true, allowedOrigins: ["images.example.com"], }, }, }, });
cf migratecarriesimages.url_transformationsover to this field.This change adds configuration and validation only.
url_transformationsis not supported inpreviews. -
#17081
08eeaf4Thanks @Naapperas! - AddretryWhileVersionNotReadable()and an optional extra-retryable predicate toretryOnAPIFailure()retryWhileVersionNotReadable(read, logger)retries a Worker version read for up to about 12 seconds while the API reports the version as not found, which can happen for a few seconds after an upload.retryOnAPIFailure()accepts a new optional last argument for treating further errors as transient. -
#16174
629f135Thanks @james-elicx! - Share static asset configuration and hashing helpers across development and deploymentThe configuration entry point now exposes asset directory validation and option resolution with caller-provided logging. The focused
@cloudflare/workers-utils/asset-hashentry point provides the content hash used by asset uploads and local Pages serving, allowing development integrations to share this behavior without depending on deployment tooling. -
#16174
629f135Thanks @james-elicx! - Add a focused configuration entry point and deprecate root configuration importsImport configuration APIs and types from
@cloudflare/workers-utils/config, including the newreadConfig()helper for reading, validating and normalizing Wrangler configuration with a caller-provided logger. The entry point also provides configuration discovery, defaults, validation, diagnostics, editing, formatting and binding interpretation helpers.Existing configuration exports from
@cloudflare/workers-utilsremain available as deprecated compatibility aliases with the same runtime values and underlying types. Change their import specifier to@cloudflare/workers-utils/config; no previously published exports are removed.
Patch Changes
-
#17031
95fd4c2Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-19Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
-
#17044
56974d4Thanks @petebacondarwin! - Warn when invocation logs are enabled while logs are disabledConfiguration validation now warns when
observability.logs.invocation_logsistrueandobservability.logs.enabledisfalse. Invocation logging remains disabled untilobservability.logs.enabledis set totrue. -
#17043
4f5b118Thanks @petebacondarwin! - Update Undici to 7.30.2 to include upstream security fixesThis 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.
@cloudflare/workers-auth@0.18.6
Patch Changes
-
#17031
95fd4c2Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-19Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
-
#17043
4f5b118Thanks @petebacondarwin! - Update Undici to 7.30.2 to include upstream security fixesThis 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.
-
Updated dependencies [
95fd4c2,be6aa81,56974d4,08eeaf4,629f135,4f5b118,629f135]:- @cloudflare/workers-utils@0.56.0
@cloudflare/vitest-plugin@1.9.0
Minor Changes
-
#16174
629f135Thanks @james-elicx! - Remove the dependency onwranglerThe Vitest plugin no longer depends on
wrangler. Reading the Wrangler configuration file, generating Miniflare options, loading local variables and serving the PagesASSETSbinding now use shared workers-sdk packages that are bundled into the plugin. Installing the plugin no longer installswrangleras well. If your project runs thewranglerCLI (for examplewrangler types), addwranglerto your owndevDependencies.
Patch Changes
-
#17031
95fd4c2Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-19Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
-
#17043
4f5b118Thanks @petebacondarwin! - Update Undici to 7.30.2 to include upstream security fixesThis 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
1b563dbThanks @petebacondarwin! - Fix remote bindings authentication with API tokens scoped to an individual WorkerRemote 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
getPlatformProxyand 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,8f45554,4f5b118,8f45554]:
@cloudflare/runtime-types@0.1.32
Patch Changes
@cloudflare/remote-bindings@0.0.69
@cloudflare/pages-functions@0.1.13
Patch Changes
-
#17031
95fd4c2Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-19Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
{ "images": { "url_transformations": { "enabled": true, "allowed_origins": ["images.example.com"] } } }