kylon-cli 0.3.9-next.692 → 0.3.9-next.693

package/README.md

@@ -121,24 +121,34 @@ The setting controls future automatic requests only. Turning it off does not
 cancel an upgrade whose drain has already started, and manual upgrades remain
 available.
 
-To upgrade manually, run the one upgrade command:
+To update manually, rerun the hosted install script — the same command that
+installed Kylon:
 
 ```bash
-kylon upgrade
+curl -fsSL https://api.kylon.io/install.sh | sh
 ```
 
-It resolves the newest build on the channel this installation tracks
-(`latest` in production, `next` on dev), compares it with the **installed**
-bundle's recorded version, and picks the owner for the host's layout: on a
-gateway host the drained service upgrade described below, on a
-credential-only host the daemon-guarded self-pin, and on a host with only an
-npm global the `npm install -g` hint (that copy stays the operator's own).
-When the installed `kylon` is too old to know the command, or is not on PATH,
-spell the same thing through npx — `npx --yes kylon-cli@latest upgrade`
-(`@next` on dev) — and the freshly-resolved copy performs the install itself
-rather than downloading itself a second time. `--force` skips the drain (see
-the interrupts below). This is the command the CLI's update notice, `kylon
-gateway status`, and the unknown-command hint all print for managed installs.
+(`https://api.purework.ai/install.sh` on dev; Windows:
+`powershell -c "irm https://api.kylon.io/install.ps1 | iex"`.) On a machine
+that already has Kylon the script never overwrites the managed bundle. It
+repairs the environment around it — a vanished Node.js gets the private
+runtime, the launcher and PATH snippet are rewritten, the serving deployment
+is re-recorded — and then asks the installed CLI to update itself with
+`kylon upgrade`. This is the command the CLI's update notice, `kylon gateway
+status`, the unknown-command hint, and the workspace's update surfaces all
+print; each spells it for the deployment the machine was set up against.
+
+`kylon upgrade` is the engine underneath the script, and can be run on its
+own when the environment is known to be healthy. It resolves the newest build
+on the channel this installation tracks (`latest` in production, `next` on
+dev), compares it with the **installed** bundle's recorded version, and picks
+the owner for the host's layout: on a gateway host the drained service
+upgrade described below, on a credential-only host the daemon-guarded
+self-pin, and on a host with only an npm global the `npm install -g` hint
+(that copy stays the operator's own). When it is already the resolved target
+— `npx --yes kylon-cli@latest upgrade` runs the newest copy — it installs
+in-process rather than downloading itself a second time. `--force` skips the
+drain (see the interrupts below).
 
 The mechanism underneath is `gateway service upgrade`:
 

package/dist/kylon-bundle.manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.3.9-next.692",
-  "fingerprint": "ab9aed0ffb274ad4ccdb746f49733e30f05a47d83816eb5cb3246faaa52015e9",
-  "source_commit": "7d476691a0f861241a2e9aede641e8cf23016c0a"
+  "version": "0.3.9-next.693",
+  "fingerprint": "5d830df462ec6aaad8d9837a4ec261625e16d97e6aabd91818976e2d676226e5",
+  "source_commit": "b43cb4927454910de308c4f820b0d12c0335091d"
 }