Back to Details

capgo-release-workflows

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Capgo Release Workflows

Capgo 发布工作流

Set up release workflows for Capacitor apps using Capgo live updates plus repository-owned build and publishing automation.
使用Capgo热更新加上代码仓库自带的构建和发布自动化能力，为Capacitor应用搭建发布工作流。

When to Use This Skill

何时使用本技能

  • User wants one release workflow covering live updates, builds, and store publishing
  • User is replacing a hosted release service with repo-owned automation
  • User wants Capgo for OTA updates and standard CI/CD for native artifacts
  • 用户想要一套覆盖热更新、构建和应用商店发布的发布工作流
  • 用户正在用代码仓库自带的自动化能力替换托管式发布服务
  • 用户想要用Capgo实现OTA更新，用标准CI/CD处理原生构建产物

Scope

适用范围

This skill coordinates three workflow areas:
  • live updates -> 
    capgo-live-updates
  • native builds -> 
    capacitor-ci-cd
  • app store publishing -> 
    capacitor-app-store
Use this skill as the top-level router when the user asks for the whole release system, not just one piece.
本技能协调三个工作流领域：
  • 热更新 -> 
    capgo-live-updates
  • 原生构建 -> 
    capacitor-ci-cd
  • 应用商店发布 -> 
    capacitor-app-store
当用户咨询完整的发布系统而非单一模块时，将本技能作为顶层路由使用。

Procedures

操作流程

Step 1: Identify Release Requirements

步骤1：明确发布需求

Determine whether the app needs:
  • OTA web updates
  • signed iOS and Android builds
  • TestFlight or Google Play publishing
  • staged channels or phased rollout
Record which parts already exist in the repository.
确定应用是否需要：
  • OTA web更新
  • 签名后的iOS和Android构建包
  • TestFlight或Google Play发布
  • 分阶段渠道或灰度发布
记录代码仓库中已经存在的相关模块。

Step 2: Set Up Live Updates

步骤2：搭建热更新能力

If OTA updates are required, use the 
capgo-live-updates
skill.
Preserve the app's release channel structure and define the rollback strategy before enabling automatic rollout.
如果需要OTA更新，请使用
capgo-live-updates
技能。
在启用自动发布前，保留应用的发布渠道结构并定义回滚策略。

Step 3: Set Up Native Build Automation

步骤3：搭建原生构建自动化能力

If the team needs reproducible native builds, use the 
capacitor-ci-cd
skill.
Keep signing, build environment variables, and version bumping under repository control.
如果团队需要可复现的原生构建，请使用
capacitor-ci-cd
技能。
将签名、构建环境变量和版本号升级逻辑交由代码仓库统一管理。

Step 4: Set Up Store Publishing

步骤4：搭建应用商店发布能力

If automated publishing is required, use the 
capacitor-app-store
skill.
Keep credentials, track selection, and release gating aligned with the current release policy.
如果需要自动化发布，请使用
capacitor-app-store
技能。
保证凭证、渠道选择和发布管控规则与当前发布策略对齐。

Step 5: Verify the End-to-End Release Flow

步骤5：验证端到端发布流程

Verify the workflow in order:
  1. native build succeeds
  2. store artifact is valid
  3. live update upload works for the matching app version
  4. rollback and channel targeting behave as expected
按以下顺序验证工作流：
  1. 原生构建成功
  2. 应用商店构建产物有效
  3. 对应应用版本的热更新上传正常运行
  4. 回滚和渠道定向功能表现符合预期

Error Handling

错误处理

  • For OTA setup issues, validate the Capgo plugin startup and rollback path before enabling broad rollout.
  • For CI/CD failures, fix signing and environment inputs before changing release logic.
  • For store publishing failures, isolate Apple and Google pipelines so one platform does not block diagnosis of the other.
  • 如遇到OTA配置问题，在大范围发布前先验证Capgo插件启动逻辑和回滚路径
  • 如遇到CI/CD失败，先修复签名和环境变量输入问题，再修改发布逻辑
  • 如遇到应用商店发布失败，将Apple和Google流水线隔离，避免其中一个平台阻碍另一个平台的问题排查