kylon-cli 0.7.11-next.1520 → 0.7.11-next.1523
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 +7 -0
- package/dist/kylon-bundle.manifest.json +3 -3
- package/dist/kylon-bundle.mjs +44 -3
- package/dist/kylon-core-bundle.mjs +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -359,6 +359,13 @@ or a fish `conf.d` drop-in; decline with `--no-modify-path`). From then on the
|
|
|
359
359
|
human terminal, the agents, and the daemon all run the same file — one
|
|
360
360
|
artifact, one version, one upgrade.
|
|
361
361
|
|
|
362
|
+
On Windows, the managed command is `kylon.exe`. It launches the pinned Node
|
|
363
|
+
runtime directly and preserves multiline text and subsequent flags without
|
|
364
|
+
passing them through CMD. It is built during installation using Windows' .NET
|
|
365
|
+
Framework C# compiler, as is the provider job shim. No PowerShell execution-policy
|
|
366
|
+
change is needed. The old managed `kylon.cmd` entry fails with migration guidance;
|
|
367
|
+
restart an existing Agent to refresh `KYLON_BIN`, or invoke `kylon.exe` directly.
|
|
368
|
+
|
|
362
369
|
A leftover npm-global or npx-cached copy stays harmless: when it starts and
|
|
363
370
|
finds a strictly newer pinned install, it defers to it automatically
|
|
364
371
|
(installer commands — `agent …` and `gateway …` — always run as invoked, so a
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
{
|
|
2
|
-
"version": "0.7.11-next.
|
|
3
|
-
"fingerprint": "
|
|
4
|
-
"source_commit": "
|
|
2
|
+
"version": "0.7.11-next.1523",
|
|
3
|
+
"fingerprint": "8a09bac1d26448ebfbfc066876db9fd198f5ded3f526b2b3d6c66a56162074ef",
|
|
4
|
+
"source_commit": "689b460932048cb86ba2076d6a445fb4e9010930"
|
|
5
5
|
}
|