kylon-cli 0.7.10-next.1385 → 0.7.10-next.1390

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 CHANGED
@@ -1291,6 +1291,30 @@ new production CLI build must be published. Service deployment alone leaves
1291
1291
  a fresh CLI-only PR from the current `main`, merge it, and dispatch stable
1292
1292
  on that commit, keeping `main` still until the CLI is published.
1293
1293
 
1294
+ - **Run the stable preflight before every stable dispatch.** A stable run
1295
+ needs about an hour and a human approval before it reaches the gates that
1296
+ most often fail, so check them first, read-only:
1297
+
1298
+ ```bash
1299
+ node scripts/ci/cli-stable-preflight.mjs --mac-host p2compat@autodeploy-bj
1300
+ ```
1301
+
1302
+ It takes the current `main` head (or `--sha <main sha>`) and prints one
1303
+ pass/fail row per gate: the merged main PR behind that commit, the newest
1304
+ production deploy and every changed file since it that is not CLI-only, the
1305
+ merged PR's latest `preview-deploy.yml` run (completed, successful, and
1306
+ merged onto `main`'s exact tree), the package version against npm `@latest`,
1307
+ any stable `cli-publish.yml` run still queued or running, the
1308
+ `p2-external-compat` macOS runner (online and idle; reading runners needs repo
1309
+ admin), and, over SSH with `--mac-host`, the harness `active-run` lock. The
1310
+ harness never steals that lock, so a held or stale one fails the row; recover
1311
+ a stale lock through `external-agent-compat-harness.yml` `recovery_run`,
1312
+ never by deleting it. The preflight dispatches, reruns and deletes nothing,
1313
+ and exits non-zero when any row fails. It cannot see qualification failures,
1314
+ Windows host state, or macOS privacy (TCC) denials for the runner service.
1315
+ On the `publish_cli=true` and `release:cli` paths the production row passes
1316
+ only after that Deploy completes; check the other rows before requesting it.
1317
+
1294
1318
  Do not `npm publish` ad hoc: use the stable workflow and its OIDC provenance.
1295
1319
  Pushing a version tag alone does not publish.
1296
1320
 
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "0.7.10-next.1385",
3
- "fingerprint": "3453eeff09da8f4390097fcc0b381f561884d4c235832b202b7489b013418e7d",
4
- "source_commit": "c8261e9a8c8525f1180688c9a69208250092db1f"
2
+ "version": "0.7.10-next.1390",
3
+ "fingerprint": "2cc0bbe1dd38eb899797b48ac9f66ce0c416b1b27cac86f6fd61d9a4f711f1bb",
4
+ "source_commit": "ec4323a86276770e5d84777f1b4efc11fcf9ba89"
5
5
  }