@collective-intelligence/cli 0.2.15 → 0.2.17
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 +13 -1
- package/dist/cli.js +12 -11
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -455,6 +455,18 @@ confirmed operation and saves a new recovery receipt. Refusal leaves the
|
|
|
455
455
|
original operation unapplied. A non-interactive run requires a fresh deployment
|
|
456
456
|
with `--allow-admin-principals`. This confirmation is independent of `--accept-breaking-changes` and is retained in recovery receipts.
|
|
457
457
|
|
|
458
|
+
A package with a Studio contribution waits for a native Studio to report ready,
|
|
459
|
+
and an unattended deploy has none. Pass `--skip-studio-readiness` to
|
|
460
|
+
`ci deploy`, `ci package install`, `ci package update` or
|
|
461
|
+
`ci package operation continue` to serve once the Backend Host is ready. The
|
|
462
|
+
switch is off by default, and neither `--non-interactive` nor `--json` implies
|
|
463
|
+
it. The Dashboard Host still gates serving, and a Host that reports `failed`
|
|
464
|
+
still fails the operation. `ci package sync` and `ci package rollback` reject
|
|
465
|
+
the switch. A Host that served without a Studio report carries
|
|
466
|
+
`hostReadiness: "skipped"` and `skippedBy` in the operation snapshot and events,
|
|
467
|
+
and the snapshot summary says `Studio readiness skipped by …`. `ci deploy` saves
|
|
468
|
+
the switch in its recovery receipt, so `--resume` replays it.
|
|
469
|
+
|
|
458
470
|
JSON mode emits newline-delimited records with `kind: progress`, `result`, or
|
|
459
471
|
`error`. An accepted operation is progress, not success. The command follows
|
|
460
472
|
resumable durable operation streams and exits successfully only after every
|
|
@@ -532,7 +544,7 @@ replay, even for the same Organization, because Backend idempotency is scoped to
|
|
|
532
544
|
the authenticated principal. The token itself is never stored.
|
|
533
545
|
The Backend still authorizes the request; a rejected/expired recovery fails and
|
|
534
546
|
never silently starts another operation. Do not combine `--resume` with
|
|
535
|
-
`--declaration`, inputs, variables, Gateway bindings, breaking-change flags
|
|
547
|
+
`--declaration`, inputs, variables, Gateway bindings, breaking-change flags, `--allow-admin-principals` or `--skip-studio-readiness`.
|
|
536
548
|
A normal deploy without `--resume` always creates a fresh invocation.
|
|
537
549
|
|
|
538
550
|
Receipts are stored under `$XDG_STATE_HOME/ci/deployments`, or
|