@capgo/cli 8.108.1 → 8.109.0

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/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@capgo/cli",
3
3
  "type": "module",
4
- "version": "8.108.1",
4
+ "version": "8.109.0",
5
5
  "description": "A CLI to upload to capgo servers",
6
6
  "author": "Martin martin@capgo.app",
7
7
  "license": "Apache 2.0",
@@ -341,7 +341,7 @@ npx @capgo/cli@latest build credentials export ANDROID_KEYSTORE_FILE \
341
341
 
342
342
  ## Cloud simulator
343
343
 
344
- A running simulator uses one native builder slot, the same limit as a native build. Stopping it records the open time as build minutes. Each session has its own URL.
344
+ A running simulator uses one native builder slot, the same limit as a native build, and counts as build time while it runs (iOS time counts double). It stops by itself after 5 minutes without input (taps, typing, installs, or `simulator command` calls) and after 40 minutes at most; the build time recorded ends when the device stopped. Stop it as soon as you are done. Each session has its own URL.
345
345
 
346
346
  ### `simulator start [appId]`
347
347
 
@@ -385,7 +385,7 @@ npx @capgo/cli@latest simulator get <session-id> com.example.app
385
385
  npx @capgo/cli@latest simulator stop <session-id> com.example.app
386
386
  ```
387
387
 
388
- Stop ends the device and records build minutes. If the device host is still running, or the minute write fails, the session stays open so the same command can be retried. A session also ends by itself after its duration, which releases the builder slot and records the capped time.
388
+ Stop ends the device and records build minutes. If the device host is still running, or the minute write fails, the session stays open so the same command can be retried. A session also ends by itself after 5 minutes without input or after 40 minutes, which releases the builder slot and records the time up to that stop. Commands sent to it after that fail with a message to start a new simulator.
389
389
 
390
390
  ## Supporting docs
391
391
 
@@ -31,9 +31,9 @@ Both MCP servers advertise five workflow guides: `check-update-health`, `ship-li
31
31
  - Background setup notices appear after a successful command and use the existing five-second shutdown budget in interactive terminals, CI, and detected AI invocations. Otherwise, human-readable piped output only shows already-ready background notices, with no added background wait. Machine modes, account-wide commands, MCP, `app todo`, `init`, and `build init` do not receive background notices. The separate AI-only `init` completion notice described below can wait up to five seconds for a fresh status request; that request is not gated on TTY status, although `init` itself requires an interactive terminal. `app todo` and explicit setup commands retain their own checklist output.
32
32
  - After supported interactive app, bundle, channel, organization, and key commands, plus `build request`, `login`, `doctor`, and `get-qr`, finish, pending background checks share a wait of up to five seconds. The CLI displays “Checking your setup...” with “Press Ctrl+C to skip.” and can exit sooner after the checks finish; pressing Ctrl-C during the wait exits immediately. CI and detected AI invocations also wait within the same budget without the banner. JSON, output-text, quiet, piped (outside CI and AI invocations), `init`, `build init`, and MCP runs do not add this background wait or banner. The separate AI-only `init` completion notice has its own five-second request budget. `account whoami` (and its `account id` alias) and `bundle releaseType` also exit without waiting.
33
33
  - On GitHub Actions (`GITHUB_ACTIONS=true`), human-facing setup notices and existing preflight trial reminders use `::notice::` annotations and append the same guidance as Markdown to `GITHUB_STEP_SUMMARY` when available. Summary write failures cannot fail the deployment. A preflight trial reminder suppresses the background setup-notice plan prompt for the same organization during that invocation; preflight reminders themselves are not deduplicated.
34
- - With analytics enabled, source scans emit `scan_started` and `scan_ended` events in the `notify-app-ready` channel with a shared `attempt_id`. The ended event includes scan duration, result, and todo-report outcome. An abandoned scan may have no ended event.
34
+ - Background onboarding scans update todos over the API when detection succeeds. They do not emit separate scan lifecycle analytics events.
35
35
  - With analytics enabled, entering the background-check wait emits `background_checks_wait_started` in the `cli-usage` channel. Its event properties include the command path, pending check count, grace period, and pending `scan_attempt_ids`. Telemetry shares the five-second wait budget and respects `CAPGO_DISABLE_TELEMETRY` and `CAPGO_DISABLE_POSTHOG`.
36
- - Updater installation checks use the same scan events and attempt pairing in the `updater-installed` channel, with a separate attempt ID from the source scan. Telemetry opt-out does not prevent either onboarding check.
36
+ - Telemetry opt-out does not prevent either onboarding check.
37
37
  - Background onboarding requests trust the default Capgo API origin. For a custom API, explicitly select the self-host with `--api-host <url>/functions/v1` where supported, or list trusted URL origins (including scheme and port) in `CAPGO_TRUSTED_API_ORIGINS`, separated by commas. Remote hosts require HTTPS; HTTP is permitted only for trusted loopback origins. Untrusted destinations and redirects are skipped without sending credentials to another host.
38
38
  - Set `CAPGO_SETUP_DEBUG=1` to diagnose background setup notices. Timing, HTTP status, scanner reports, shutdown deadlines, and suppression reasons go to stderr; credentials and response bodies are omitted. Keep stdout attached to your terminal when investigating the five-second wait: outside CI and AI invocations, piping or redirecting stdout skips it.
39
39
  - Shared public flags commonly include `-a, --apikey <apikey>` and `--verbose` on commands that support verbose output.