wrangler@4.139.0

Summary

Minor Changes #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. Patch Changes #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 ]: miniflare@5.20260923.0-alpha

Lotu Radar provides attributed news summaries and links to the original publisher. Full reporting and copyright remain with the source.