Back to Details

capgo-release-management

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Capgo Release Management

Capgo 发布管理

Use this skill for Capgo OTA bundle, channel, and encryption-key workflows.
本技能适用于Capgo OTA包、渠道和加密密钥相关工作流。

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
  • 用户想要上传或管理Capgo包
  • 用户需要渠道定向或兼容性检查
  • 用户想要对包进行加密或清理操作

Procedures

操作流程

Step 1: Choose the Release Operation

步骤1：选择发布操作

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
使用对应的命令组：
  • 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

步骤2：上传或检查包

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.
推荐使用最新版Capgo CLI：
bash
npx @capgo/cli@latest bundle upload com.example.app --path ./dist --channel production
当用户不确定某个包是否可以安全发布时，在变更渠道前先执行兼容性检查。

Step 3: Manage Channels

步骤3：管理渠道

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

步骤4：设置加密

Use 
key create
or 
key save
before encrypted bundle uploads.
Keep private keys out of version control.
在上传加密包之前，先执行
key create
或
key save
命令。
请勿将私钥提交到版本控制系统中。

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.
  • 若上传失败，重试前先检查包版本是否唯一、渠道选择是否正确
  • 若兼容性检查失败，强制发布前先检查包元数据和原生版本约束
  • 若加密上传出现问题，轮换密钥前先验证公钥和会话密钥流程是否正常