Repository navigation
Update dependency wrangler to v4.166.0 - #9
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Author
|
renovate
Bot
force-pushed
the
renovate/wrangler-4.x
branch
from
November 3, 2026 15:22
99d2359 to
35ad13a
Compare
renovate
Bot
force-pushed
the
renovate/wrangler-4.x
branch
from
November 7, 2026 20:13
35ad13a to
4a361c7
Compare
renovate
Bot
force-pushed
the
renovate/wrangler-4.x
branch
from
November 12, 2026 08:12
4a361c7 to
acc7b82
Compare
renovate
Bot
force-pushed
the
renovate/wrangler-4.x
branch
from
November 15, 2026 22:47
acc7b82 to
c8e44ea
Compare
renovate
Bot
force-pushed
the
renovate/wrangler-4.x
branch
from
November 21, 2026 12:17
c8e44ea to
c9676a5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
4.156.1→4.166.0Release Notes
cloudflare/workers-sdk (wrangler)
v4.166.0Compare Source
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:{ "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: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:
#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,4f5b118,629f135,8f45554]:v4.165.0Compare Source
Minor Changes
#10598
24bd3c3Thanks @Ehbraheem! - Add a new--forceflag tod1 migrations applywhich skips the interactive confirmation and applies any pending migrations non-interactively. This is useful for CI and automation.Usage example:
Fixes #5017
Patch Changes
#16019
8f26e90Thanks @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
3595295Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-18Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#17003
3595295Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#16719
f833c8aThanks @jaeminbird! - Report.dev.varsand.envfiles that are not UTF-8 instead of silently loading no variablesBefore Wrangler would incorrectly read non UTF-8
.dev.varsand.envfiles as UTF-8. A.dev.varsfile that is not UTF-8 now stopswrangler devwith a message that says how to fix it, and a.envfile that is not UTF-8 is skipped with a warning. UTF-8 files, with or without a BOM, load as before.#14334
67d7c0aThanks @Divkix! - Replace the unmaintained asset hashing dependency withhash-wasmKeep asset hashes unchanged for Workers and Pages deployments and local Pages development while using a maintained WebAssembly implementation.
#16949
110c162Thanks @edmundhung! - Fail remote RPC binding requests on network errors instead of hangingRemote 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
6750663Thanks @penalosa! - Fix TypeScript errors when importing Wrangler's APIsProjects that import Wrangler's APIs, such as
getPlatformProxyordefineWranglerConfig, can now type-check withskipLibCheck: 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]:v4.164.0Compare Source
Minor Changes
#16450
5f05841Thanks @xortive! - Add custom CA and client certificate references to Workers VPC service TLS settingsWorkers VPC (open beta) service create and update commands accept
--certificate-authorityand--client-certificateUUIDs. 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 withdisabled; 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.Create an HTTPS service with both a custom trust chain and an mTLS client certificate, or a PostgreSQL TCP service with only a custom CA:
For client-certificate-only configuration, use
--client-certificate <client-uuid> --cert-verification-mode verify_fullinstead 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:To 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:Patch Changes
#16974
77b5ca7Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-17Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16974
77b5ca7Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
Updated dependencies [
77b5ca7,77b5ca7,51064e6]:v4.163.0Compare Source
Minor Changes
#16917
d36b39dThanks @jamesopstad! - Write Build Output to.cloudflare/output/v1/and record the producervite buildand the experimentalwrangler build --experimental-cf-build-outputnow write Build Output v1, with account settings nested undersettingsin the rootconfig.json. They also record themselves as theproducer, 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
349fc4eThanks @leostera! - Start local Workflows from Artifacts eventsDeclare Artifacts events on
exports.workflow({ name, events })incloudflare.config.tsto start the owning Workflow locally incf, Vite, and Workers Vitest. Wrangler configurations continue to usetriggers.events. Native config conversion derives those targets from the Workflow export, andcf migrateattaches 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.Patch Changes
#16803
b219078Thanks @petebacondarwin! - Run experimental cf projects with their installed Vite or Vite+ commandscf 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 internalcf-vitedelegate 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-pluginin its own manifest, or addviteorvite-plusas 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--configare evaluated by Vite when the command runs. Existing framework commands keep their priority. Consumers resolve bare executables using the detectednodeModulesPathsin order, adding.binto each directory. Lookup stops at the validated workspace root; standalone applications use only their ownnode_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.cjsand.ctsVite configs to ESM imports and exports in.mjsor.mtsbefore 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
db3c071Thanks @danlapid! - Stopwrangler devfrom missing config file changes made soon after a reloadwrangler devreplaced 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
81e56ddThanks @benbuzbee! - Use the effectivemax_instancesvalue when choosing the default container rollout stepsWhen
max_instanceswas 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 omittedmax_instances, while still using a single 100% step whenmax_instancesis 0 or 1.#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16946
e97c9f8Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#16874
4335eacThanks @petebacondarwin! - Avoid redundant OAuth refreshes after a sibling process updates credentialsCheck 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
d36b39dThanks @jamesopstad! - Detect Cloudflare Build Output of any version before deployingwrangler deploy,wrangler versions uploadandwrangler previewrefuse to run in a project that has Cloudflare Build Output, because that output belongs tocf. 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 newercfis still caught.Updated dependencies [
e97c9f8,e97c9f8,349fc4e,0bf81ac]:v4.162.0Compare Source
Minor Changes
#16735
f005593Thanks @leostera! - Use the local simulator for Artifacts bindings that omitremoteBehavior change: Artifacts bindings now default to the local simulator during development, like KV, R2 and D1. Previously, an omitted
remotein Wrangler and the Vite plugin used the deployed Artifacts resource. If you want deployed repos inwrangler devorvite dev, set"remote": trueon the binding (dev: { remote: true }incloudflare.config.ts). Artifacts is in beta, so this ships as a minor release.While
remoteis 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. Setremote: trueto use deployed repos, orremote: falseto silence this warning." Workers Vitest andwrangler dev --localalready 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
032f8c2Thanks @vaishnav-mk! - Reject settings on aworkflowsbinding to a Workflow declared inexportsA
workflowsbinding can still bind a Workflow that the Worker declares inexports, but it can no longer setlimits,concurrency,schedules,default_retention, orjurisdictionfor 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
032f8c2Thanks @vaishnav-mk! - Upload Workflow export settings with the Workerwrangler deployandwrangler versions uploadnow include the settings of eachworkflowexport (limits,concurrency,schedules,default_retention, andjurisdiction) in the upload, instead of sending only its type and name. Uploads of a Worker withworkflowexports also send aCloudflare-Workers-Script-Api-Dateheader, which lets the Workers API provision Workflow exports from these settings as part of the upload.wrangler deployandwrangler triggers deploystill 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 deploynow explains that scheduled Workflows require a paid Workers plan.Patch Changes
#16849
3cea40bThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-12Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16886
63eb6daThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-13Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16849
3cea40bThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#16886
63eb6daThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#16864
3b1b408Thanks @MattieTK! - Fix packages with nestedpackage.jsonfiles missing from deploy metadataPackages such as
hono,stripeand@modelcontextprotocol/sdkwere silently omitted from the package dependency metadata reported duringwrangler deployandwrangler versions upload. These packages are now included with their installed versions. Autoconfig and codemods also detect their installed versions correctly.#16862
c889551Thanks @petebacondarwin! - Fix requests hanging when a local Worker reload finishes before an inflight request failsWrangler 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]:v4.161.0Compare Source
Minor Changes
#16840
8b2a363Thanks @jamesopstad! - Write source maps in Build Output withsourcesrelative to each source map fileThis changes the experimental Build Output that
wrangler build --experimental-cf-build-outputandcf-wrangler buildwrite. Their source maps were prepared as if for upload, withsourcesrelative 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 inbundle/to the original files, like the source maps the Vite plugin writes.Patch Changes
#16833
5f539b5Thanks @jamesopstad! - Namecfcommands andcloudflare.config.tssettings in remote bindings errors fromcf-wranglerWhen
cfruns development through thecf-wranglerdelegate and remote bindings cannot be authenticated, the error now tells you to runcf auth whoami,cf auth logoutandcf auth logininstead 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'sidsetting instead ofapp_id, and suggestscf flagship apps create.wrangler devstill names Wrangler's commands and settings.#16527
dc47e6dThanks @petebacondarwin! - Normalize relative redirect pathnames consistently across Pages and Workers assetsRelative
_redirectstargets 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
575d136Thanks @edmundhung! - Update@netlify/build-infoto 11.3.1#16838
3626ee8Thanks @jamesopstad! - Keep the remote bindings session when you remove the last remote bindingWhen you removed the last remote binding while
wrangler devwas running, Wrangler restarted the remote bindings session with credentials that ignored--profileand theaccount_idin 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]:v4.160.1Compare Source
Patch Changes
877b249,69e650c]:v4.160.0Compare Source
Minor Changes
#16760
cb9534fThanks @petebacondarwin! - Support forwarded Wrangler development server options in the experimentalcf-wranglerdelegatecf devcan now forward options such as--inspector-port 9229,--ip,--var, and--persist-toto the Wrangler development runtime. The delegate reuses Wrangler's dev option definitions and validation while retaining project config discovery,--modeenvironment selection, local development, and its.cloudflare/statedefault. 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 examplecf dev -- --local --persist-to "custom state". Config and script overrides, whole-worker remote development, and Wrangler's global options remain unsupported.#16739
6af492eThanks @GregBrimble! - Add custom Cloudflare API headers throughCLOUDFLARE_API_HEADERSSet
CLOUDFLARE_API_HEADERSto 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.Patch Changes
#16810
cdc970bThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-10Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16810
cdc970bThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
| Dependency | From | To |
| -----------------------------------------
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.