Patch Changes
-
#16370
61fc739Thanks @WalshyDev! - Fetch the remote config diff from the configured compliance regionWhen a Worker was last deployed from the dashboard,
wrangler deployandwrangler versions uploaddownload its remote configuration to compare with the local one. These requests ignored thecompliance_regionfield in the Wrangler configuration file and only honoured theCLOUDFLARE_COMPLIANCE_REGIONenvironment variable. A FedRAMP High Worker configured through the config file would send them toapi.cloudflare.cominstead ofapi.fed.cloudflare.com, and the deploy would fail with authentication errors. They now use the same compliance region as the rest of the deploy. -
#16359
262021dThanks @tw4! - Stop--strictdeploys and version uploads from aborting when the API omits optional binding fieldsPreviously,
wrangler deploy --strictandwrangler versions upload --strictcould report a destructive change for an unchanged configuration, for example an R2 bucket in the default jurisdiction, because a field the API left out was compared as removed. Missing and unset optional fields are now treated as equal, so these commands proceed when the local configuration matches the deployed Worker. -
Updated dependencies [
3464abc,017bf9b]:- miniflare@5.20261019.1-beta
- @cloudflare/workers-utils@0.47.3
- @cloudflare/cli-shared-helpers@0.2.7
- @cloudflare/config@0.27.0
- @cloudflare/containers-shared@0.23.1