wrangler@4.143.1

Summary

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

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