@astrale-os/adapter-cloudflare 0.5.0-beta.173 → 0.5.0-beta.174

package/README.md

@@ -81,7 +81,6 @@ label.
   deployment lives in (AM-174). Which namespaces a deployment may bind is its host's to decide.
   `durable` is frozen into the configuration (`settings.durableOptions`, AM-175), so into the
   label, and bound in `ASTRALE_SETTINGS`: a durable run stays on the deployment that started it.
-  `astrale-domain dev` serves only direct-mode Environments.
 
 ## Legacy direct mode
 
@@ -92,11 +91,10 @@ whose `prod` binds an EU-jurisdiction R2 bucket that namespace mode does not adm
 `beta`, `prod` and `development` environments and its frozen `admin-beta`; the Shell and its frozen
 `legacy-v3`; and ui:domain.
 
-`astrale-domain dev <environment>` builds locally and deploys each admitted Worker and frontend
-update remotely through the same path as `deploy`; it starts no local Worker, Vite server, or
-tunnel. Omitting `route` uses the observed stable `*.workers.dev` issuer.
+`astrale-domain deploy <environment>` builds locally and deploys the Worker and frontend
+remotely. Omitting `route` uses the observed stable `*.workers.dev` issuer.
 
-One watcher serializes its own updates. For an existing Worker, it uploads a candidate, reconciles
+For an existing Worker, a deploy uploads a candidate, reconciles
 configured triggers, and stages the candidate at 0% while the previous version retains 100% of normal
 HTTP traffic. Exact-version probes verify Publication, Bundle, and serving identity before promotion;
 serving the Publication also initializes the Domain Runtime. After promotion, normal requests

package/dist/index.d.ts

@@ -14,7 +14,7 @@
  * With `namespace`, each release becomes one immutable deployment in that platform dispatch
  * namespace, at `https://<label>.<routingDomain>`. Without it, the Environment is on the legacy
  * direct mode (deprecated): one stable Worker on `route` or `*.workers.dev`, replaced in place by
- * each deploy, which `astrale-domain dev <environment>` also serves.
+ * each `astrale-domain deploy <environment>`.
  *
  * Prefer a managed deploy (no Cloudflare account)? Use `@astrale-os/adapter-astrale`, which builds
  * the same bundle via this package's `/build` toolkit and ships it through the Astrale platform. A

package/dist/index.js

@@ -14,7 +14,7 @@
  * With `namespace`, each release becomes one immutable deployment in that platform dispatch
  * namespace, at `https://<label>.<routingDomain>`. Without it, the Environment is on the legacy
  * direct mode (deprecated): one stable Worker on `route` or `*.workers.dev`, replaced in place by
- * each deploy, which `astrale-domain dev <environment>` also serves.
+ * each `astrale-domain deploy <environment>`.
  *
  * Prefer a managed deploy (no Cloudflare account)? Use `@astrale-os/adapter-astrale`, which builds
  * the same bundle via this package's `/build` toolkit and ships it through the Astrale platform. A

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@astrale-os/adapter-cloudflare",
-  "version": "0.5.0-beta.173",
+  "version": "0.5.0-beta.174",
   "description": "Deploy an Astrale Domain through Cloudflare Workers",
   "keywords": [
     "adapter",
@@ -57,7 +57,7 @@
     "registry": "https://registry.npmjs.org/"
   },
   "dependencies": {
-    "@astrale-os/sdk": "0.6.0-beta.18",
+    "@astrale-os/sdk": "0.6.0-beta.19",
     "@noble/hashes": "2.3.0",
     "@restatedev/restate-sdk-cloudflare-workers": "1.17.0",
     "hono": "^4.6.20",