Capgo Release Management

by cap-go2cfb277a1488No license72 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Guides the agent through Capgo OTA release workflows including bundle uploads, compatibility checks, channels, cleanup, and encryption key setup. Use when managing Capgo bundle and channel operations. Do not use for native build requests or organization administration.

Instructions onlyDevOps & Cloud
AI-generated overview

Guides Capgo OTA release workflows: bundle uploads, compatibility checks, channels, cleanup and encryption keys.

What it does
This skill provides step-by-step guidance for Capgo over-the-air release operations. It covers choosing the right command group for bundle upload, listing, deletion and cleanup, running compatibility and release-type checks, managing channels and their default bundle, and setting up encryption keys before encrypted uploads. It also lists error-handling checks for upload, compatibility and encrypted-upload failures.
When to use it
Use it when a user wants to upload or manage a Capgo bundle, target channels, verify bundle compatibility before rollout, or configure bundle encryption and cleanup. It is not intended for native build requests or organization administration.
Requirements
Requires the Capgo CLI, invoked in the instructions via npx @capgo/cli@latest, and network access to Capgo services. Encryption workflows need key material, and private keys must be kept out of version control. The skill ships no scripts; it is instructions only.

Capgo Release Management

Use this skill for Capgo OTA bundle, channel, and encryption-key workflows.

When to Use This Skill

  • User wants to upload or manage a Capgo bundle
  • User needs channel targeting or compatibility checks
  • User wants bundle encryption or cleanup

Procedures

Step 1: Choose the Release Operation

Use the matching command group:

  • bundle upload/list/delete/cleanup
  • bundle compatibility/releaseType/zip/encrypt/decrypt
  • channel add/list/delete/set/currentBundle
  • key save/create/delete_old

Step 2: Upload or Inspect Bundles

Prefer the current Capgo CLI:

bash
npx @capgo/cli@latest bundle upload com.example.app --path ./dist --channel production

Use compatibility checks before channel changes when the user is unsure whether a bundle is safe for rollout.

Step 3: Manage Channels

Use channel operations to set defaults, target specific bundles, and control rollout scope.

Only change the default channel when the user explicitly intends to move production traffic.

Step 4: Set Up Encryption

Use key create or key save before encrypted bundle uploads.

Keep private keys out of version control.

Error Handling

  • For upload failures, verify bundle version uniqueness and channel selection before retrying.
  • For compatibility failures, inspect package metadata and native version constraints before forcing a rollout.
  • For encrypted upload issues, verify the public key and session key flow before rotating keys.

Source and attribution

Source:cap-go/capgo-skillsinskills/capgo-release-managementat commit2cfb277

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal