@astrale-os/adapter-cloudflare 0.5.0-beta.73 → 0.5.0-beta.74

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [0.5.0-beta.74](https://github.com/astrale-os/sdk/compare/adapter-cloudflare-v0.5.0-beta.73...adapter-cloudflare-v0.5.0-beta.74) (2026-08-28)
+
+
+### Bug Fixes
+
+* **adapter-cloudflare:** bypass fresh tunnel DNS propagation ([#313](https://github.com/astrale-os/sdk/issues/313)) ([9a71196](https://github.com/astrale-os/sdk/commit/9a71196cf9bed1e2c27402ee893b44df3dd42d3f))
+
+
+### Dependencies
+
+* The following workspace dependencies were updated
+  * dependencies
+    * @astrale-os/sdk bumped to 0.5.0-beta.71
+
 ## [0.5.0-beta.73](https://github.com/astrale-os/sdk/compare/adapter-cloudflare-v0.5.0-beta.72...adapter-cloudflare-v0.5.0-beta.73) (2026-08-28)
 
 

package/dist/development/resolved-fetch.d.ts

@@ -8,10 +8,9 @@ export interface ResolvedFetchDependencies {
     readonly request: RequestAddress;
 }
 /**
- * Fetch one HTTPS origin through authoritative A records instead of the host
- * process' getaddrinfo cache. Quick Tunnel hostnames can be negatively cached
- * when their URL is observed milliseconds before DNS propagation; retrying
- * global fetch in that process then remains stuck even after the record exists.
+ * Fetch one HTTPS origin through the stable TryCloudflare edge addresses.
+ * Fresh Quick Tunnel hostnames can remain absent from DNS after the connector
+ * is registered, while TLS SNI and Host already route through the stable edge.
  */
 export declare function resolvedHttpsFetch(origin: string, dependencies?: ResolvedFetchDependencies): ReadinessFetch;
 declare function requestAddress(url: URL, address: string, init: Parameters<ReadinessFetch>[1]): Promise<Response>;

package/dist/development/resolved-fetch.js

@@ -6,23 +6,25 @@ const defaults = Object.freeze({
     request: requestAddress,
 });
 /**
- * Fetch one HTTPS origin through authoritative A records instead of the host
- * process' getaddrinfo cache. Quick Tunnel hostnames can be negatively cached
- * when their URL is observed milliseconds before DNS propagation; retrying
- * global fetch in that process then remains stuck even after the record exists.
+ * Fetch one HTTPS origin through the stable TryCloudflare edge addresses.
+ * Fresh Quick Tunnel hostnames can remain absent from DNS after the connector
+ * is registered, while TLS SNI and Host already route through the stable edge.
  */
 export function resolvedHttpsFetch(origin, dependencies = defaults) {
     const expected = new URL(origin);
     if (expected.protocol !== 'https:') {
         throw new TypeError('Resolved development fetch requires an HTTPS origin.');
     }
+    const resolutionHost = expected.hostname.endsWith('.trycloudflare.com')
+        ? 'trycloudflare.com'
+        : expected.hostname;
     let addresses;
     let cursor = 0;
     return async (input, init) => {
         const url = new URL(input);
         if (url.origin !== expected.origin)
             return fetch(input, init);
-        const resolved = addresses ?? (await dependencies.resolve(expected.hostname));
+        const resolved = addresses ?? (await dependencies.resolve(resolutionHost));
         if (resolved.length === 0)
             throw new Error(`No IPv4 address resolved for ${expected.hostname}.`);
         addresses = resolved;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@astrale-os/adapter-cloudflare",
-  "version": "0.5.0-beta.73",
+  "version": "0.5.0-beta.74",
   "description": "Deploy an Astrale application through Cloudflare Workers",
   "keywords": [
     "adapter",
@@ -49,7 +49,7 @@
     "registry": "https://registry.npmjs.org/"
   },
   "dependencies": {
-    "@astrale-os/sdk": "0.5.0-beta.70",
+    "@astrale-os/sdk": "0.5.0-beta.71",
     "@noble/hashes": "2.3.0",
     "hono": "^4.6.20",
     "jose": "^6.1.3",