nope, the ci pipline is failing with this error
nope, the ci pipline is failing with this error



example.org, client1.org & client2.org. Recently, when publishing the Worker, we started to experience the error :
Route pattern must include zone name: example.org [code: 10022]afaik that error means you don't have CF For SaaS enabled on the zone you're trying to add the route on

Total Upload: 10.17 KiB / gzip: 2.57 KiB

wrangler deploy --var GH_SHA=$GITHUB_SHAwrangler deployRequest.signal API (https://developer.mozilla.org/en-US/docs/Web/API/Request/signal) would be a convenient API to utilise for signalling when the client has disconnected. Currently we have no what of detecting when the request has been cancelled. Particularly important for SSE/streaming scenarios.ctx.addEventListener('end', () => {}).ctx.waitUntil() then it stays alive but we have no way of knowing when the client has disconnected. Request.signal is an existing API which currently does nothing. The Workers runtime could "abort" that signal when the client disconnects, as a convenient signal if scripts want to know.
routes = [
{ pattern="*/cdn/*", zone_id="xxxxxxId" }
]example.org is our domain
client1.org CNAME cname.example.org -> client1 domain connected to ours
client2.org CNAME cname.example.org -> client2 domain connected to oursexample.orgclient1.orgclient2.orgRoute pattern must include zone name: example.org [code: 10022]wrangler deploy --var GH_SHA=$GITHUB_SHAwrangler deploy Total Upload: 3324.79 KiB / gzip: 1022.32 KiB
Worker Startup Time: 235 ms
Your worker has access to the following bindings:
- KV Namespaces:
- CACHIFIED_CACHE: 191f201005724b038b6facd2ae37e1d9
- Services:
- PUBLIC_DATA_SERVICE: 🔴 naamdeo-courses-api#PublicDataService
- AUTHENTICATED_USER_SERVICE: 🔴 naamdeo-courses-api#AuthenticatedUserService
- RESTRICTED_SERVICE: 🔴 naamdeo-courses-api#RestrictedServiceRequest.signalRequest.signalctx.addEventListener('end', () => {})ctx.waitUntil()