@capgo/cli 8.108.2 → 8.109.1

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.2",
4
+ "version": "8.109.1",
5
5
  "description": "A CLI to upload to capgo servers",
6
6
  "author": "Martin martin@capgo.app",
7
7
  "license": "Apache 2.0",
@@ -9,7 +9,7 @@ Use this skill for Capgo Cloud native iOS and Android build workflows.
9
9
 
10
10
  Capgo Build is generally available for production releases on both platforms. It works from Windows, Linux, macOS, and CI without a local Mac or Xcode. One CLI supports guided signing, live logs, downloadable artifacts, and optional App Store Connect and Google Play submission.
11
11
 
12
- For AI-assisted signing setup, [configure your agent's MCP client](https://capgo.app/docs/cli/reference/mcp/) to launch `npx @capgo/cli@latest mcp`. Once connected, use the local MCP `start_capgo_builder_onboarding` tool and follow its `next` instructions. If that tool is unavailable, run `npx @capgo/cli@latest build init` in a terminal in your Capacitor project. For a configured project, use `capgo_request_build`, then inspect status and logs. The hosted MCP supports archive upload and build start as separate steps; follow its tool instructions. Never paste signing secrets into chat.
12
+ For AI-assisted signing setup, [configure your agent's MCP client](https://capgo.app/docs/cli/reference/mcp/) to launch `npx @capgo/cli@latest mcp`. Once connected, use the local MCP `start_capgo_builder_onboarding` tool and follow its `next` instructions. If that tool is unavailable, run `npx @capgo/cli@latest build init` in a terminal in your Capacitor project. If the Capgo app ID is already used by another organization, ask the user to approve a different Capgo app ID before changing any file. Do not change the native `appId`. Save the approved ID only in `plugins.CapgoBuilder.capgoBuilderAppId`. For a configured project, use `capgo_request_build`, then inspect status and logs. The hosted MCP supports archive upload and build start as separate steps; follow its tool instructions. Never paste signing secrets into chat.
13
13
 
14
14
  Use [current pricing](https://capgo.app/pricing/) for included minutes and prepaid credits, and [public build data](https://capgo.app/builder-data/) for measured performance. Do not invent speed or success-rate claims. Store accounts, signing permissions, and store review requirements still apply.
15
15
 
@@ -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.
@@ -44,7 +44,7 @@ Both MCP servers advertise five workflow guides: `check-update-health`, `ship-li
44
44
  ### Project setup and diagnostics
45
45
 
46
46
  - For MCP OTA setup, call `start_capgo_live_update_onboarding` first and follow `next`. At `setup-encryption`, use the app purpose and bundle contents already known from the conversation or project to explain a recommendation; do not ask the user to repeat known details. Recommend `skip` for most apps, including public quotes, news, and catalogs. Recommend `enable` only for an explicit user request or a concrete requirement for end-to-end encrypted delivery of the code/assets. Sensitive runtime/API data alone does not require bundle encryption. Explain private-key backup, CI key configuration, and the native rebuild, then wait for the user's choice. Never enable encryption just as a conservative default.
47
- - `init [apikey] [appId]`: when the app has a supported Builder-only checklist assigned by Capgo, continues with `build init` and its existing credential/resume flow before OTA setup. OTA-only and dual-assigned apps retain the existing setup flow. For other assignments, provides guided first-time setup for Capgo in a Capacitor app. The interactive flow now runs as a real Ink-based fullscreen onboarding so it uses the same UI stack as `build init` (alias: `build onboarding`), with a persistent dashboard, phase roadmap, progress cards, shared log area, and resume support. At startup, onboarding still recommends a clean git worktree before file edits; dirty repos show `Check again` first and also offer a non-recommended `Continue anyway` override. When dependency auto-detection fails on macOS, the flow opens a native file picker for `package.json` before falling back to manual path entry. If the onboarding bundle upload fails, recovery can retry immediately or ask for the app's `package.json` and optional installed-dependency paths (app-local or hoisted `node_modules`) and then retry. If the local bundle ID already exists in the selected Capgo account, onboarding offers to reuse that app, then offers to delete and recreate it, then falls back to alternate bundle ID suggestions. If the user reuses a pending app that was already created in the web onboarding flow, the CLI syncs that selected dashboard app ID back into `capacitor.config.*` before the remaining steps continue. Outside that reused pending-app path, the CLI keeps using the local Capacitor app ID. It writes the new `autoUpdate` policy modes into config: `"atBackground"` for the default flow and `"always"` for instant updates. It can also offer a final `npx skills add https://github.com/Cap-go/capgo-skills -g -y` install step before the GitHub support prompt; if accepted, the support menu includes `Cap-go/capgo-skills` alongside the updater-only and all-Capgo choices. If native platforms are missing, the onboarding can offer to run `cap add` for you. The updater step now verifies that `@capgo/capacitor-updater` is both declared in the selected `package.json` and resolvable from `node_modules`; if automatic install or later build/sync fails, onboarding prints the manual command, waits for the user to type `ready`, re-checks, and only then continues. If the user enables instant updates, onboarding requires `@capacitor/splash-screen` for `autoSplashscreen`, offers to install it with the same auto-install/retry flow, and waits until it is declared and resolvable before writing config. During the iOS run-on-device step, onboarding asks whether to use a physical iPhone/iPad or a simulator; for physical devices, it asks the user to connect and unlock the device, then offers a check-again loop before launching with the detected target. If iOS sync validation fails during onboarding, the CLI can offer to run a one-line native reset command, wait for you to type `ready` after a manual fix, surface `doctor`, and save a support bundle before you leave the flow.
47
+ - `init [apikey] [appId]`: when the app has a supported Builder-only checklist assigned by Capgo, continues with `build init` and its existing credential/resume flow before OTA setup. OTA-only and dual-assigned apps retain the existing setup flow. For other assignments, provides guided first-time setup for Capgo in a Capacitor app. The interactive flow now runs as a real Ink-based fullscreen onboarding so it uses the same UI stack as `build init` (alias: `build onboarding`), with a persistent dashboard, phase roadmap, progress cards, shared log area, and resume support. At startup, onboarding still recommends a clean git worktree before file edits; dirty repos show `Check again` first and also offer a non-recommended `Continue anyway` override. When dependency auto-detection fails on macOS, the flow opens a native file picker for `package.json` before falling back to manual path entry. If the onboarding bundle upload fails, recovery can retry immediately or ask for the app's `package.json` and optional installed-dependency paths (app-local or hoisted `node_modules`) and then retry. If the Capgo app ID already exists in the selected Capgo account, onboarding offers to reuse that app, then offers to delete and recreate it, then asks the user to approve a different Capgo app ID before writing anything. The native bundle ID stays unchanged. The approved ID is saved only in `plugins.CapacitorUpdater.appId`. If the user reuses a pending app that was already created in the web onboarding flow, the CLI syncs that selected dashboard app ID back into `capacitor.config.*` before the remaining steps continue. Outside that reused pending-app path, the CLI keeps using the local Capacitor app ID. It writes the new `autoUpdate` policy modes into config: `"atBackground"` for the default flow and `"always"` for instant updates. It can also offer a final `npx skills add https://github.com/Cap-go/capgo-skills -g -y` install step before the GitHub support prompt; if accepted, the support menu includes `Cap-go/capgo-skills` alongside the updater-only and all-Capgo choices. If native platforms are missing, the onboarding can offer to run `cap add` for you. The updater step now verifies that `@capgo/capacitor-updater` is both declared in the selected `package.json` and resolvable from `node_modules`; if automatic install or later build/sync fails, onboarding prints the manual command, waits for the user to type `ready`, re-checks, and only then continues. If the user enables instant updates, onboarding requires `@capacitor/splash-screen` for `autoSplashscreen`, offers to install it with the same auto-install/retry flow, and waits until it is declared and resolvable before writing config. During the iOS run-on-device step, onboarding asks whether to use a physical iPhone/iPad or a simulator; for physical devices, it asks the user to connect and unlock the device, then offers a check-again loop before launching with the detected target. If iOS sync validation fails during onboarding, the CLI can offer to run a one-line native reset command, wait for you to type `ready` after a manual fix, surface `doctor`, and save a support bundle before you leave the flow.
48
48
  - When `init` enters OTA setup, it enables the app's missing OTA dashboard checklist without resetting existing progress or removing Builder tasks. Checklist activation is independent of analytics; Builder-only handoffs do not activate OTA.
49
49
  - `init --no-analytics`: disables init onboarding analytics and terminal replay for that run.
50
50
  - After successful OTA `init`, detected AI sessions receive the plain next-steps notice (or the trial line alone) after the terminal UI closes. It uses the final selected app and authenticated API client, waits at most five seconds, and remains visible even if a trial warning appeared earlier. Ordinary terminal sessions receive no additional footer; analytics opt-out does not suppress it.