kylon-cli 0.3.8 → 0.3.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +29 -2
- package/dist/kylon-bundle.mjs +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -97,6 +97,28 @@ fresh `npx` can still install itself over an older pinned copy; set
|
|
|
97
97
|
|
|
98
98
|
### Upgrading a local runtime
|
|
99
99
|
|
|
100
|
+
Automatic Kylon CLI updates are enabled by default for each enrolled computer.
|
|
101
|
+
The server checks an online computer for an eligible update at most once every
|
|
102
|
+
four hours. When it rolls an exact published version out to that computer, the
|
|
103
|
+
daemon uses the same drain-restart path as a manual upgrade: it waits for active
|
|
104
|
+
agent work to finish, installs the managed bundle under `~/.kylon/bin`, and
|
|
105
|
+
restarts onto it. The server never requests `--force` automatically.
|
|
106
|
+
|
|
107
|
+
The owner can change the setting under **Settings → Developer tools → Kylon
|
|
108
|
+
CLI → Authorized devices**, or from that computer:
|
|
109
|
+
|
|
110
|
+
```bash
|
|
111
|
+
kylon gateway auto-update status
|
|
112
|
+
kylon gateway auto-update on
|
|
113
|
+
kylon gateway auto-update off
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
The setting controls future automatic requests only. Turning it off does not
|
|
117
|
+
cancel an upgrade whose drain has already started, and manual upgrades remain
|
|
118
|
+
available.
|
|
119
|
+
|
|
120
|
+
To upgrade manually:
|
|
121
|
+
|
|
100
122
|
```bash
|
|
101
123
|
npx --yes kylon-cli@latest gateway service upgrade
|
|
102
124
|
```
|
|
@@ -151,8 +173,13 @@ for the debugger-friendly tsx-based dev loop.
|
|
|
151
173
|
|
|
152
174
|
### Release channels
|
|
153
175
|
|
|
154
|
-
npm dist-tags
|
|
155
|
-
policy
|
|
176
|
+
npm dist-tags remain the publication pointer. A separate server runtime-config
|
|
177
|
+
policy (`cli_auto_update/latest` and `cli_auto_update/next`) selects an exact
|
|
178
|
+
currently published target plus a 0-100% stable per-computer rollout for
|
|
179
|
+
automatic updates. A missing, disabled, mismatched, or 0% policy sends no
|
|
180
|
+
automatic request; manual upgrades still resolve the dist-tag normally.
|
|
181
|
+
|
|
182
|
+
Every merge to `develop` publishes a prerelease to the `next` tag
|
|
156
183
|
(`.github/workflows/cli-publish.yml`). A production deployment dispatched from
|
|
157
184
|
`main` automatically invokes the same workflow in stable mode and publishes the
|
|
158
185
|
exact `packages/cli/package.json` version to `latest`; it is idempotent when that
|