wrangler@4.147.0

Summary

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

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