Capgo Release Workflows

Set up an end-to-end release system: Capgo OTA for web changes, native builds for binary changes, store publishing, and a CI gate that picks the right path.

When to Use

TRIGGER when:

• The user wants a single release pipeline covering live updates, native builds, and store publishing.
• The user is moving off a hosted release service (Appflow-style) to CI they own.
• The user asks "how does CI know if this needs a store release?"

Do not use when:

• The user needs one operation (upload or promote a bundle, request one build). Use capgo-release-management or capgo-native-builds.
• The user is wiring the updater plugin. Use capgo-live-updates.
• The user is migrating off Ionic Appflow specifically. Start with ionic-appflow-migration, then return here for the pipeline.
• The app is not Capacitor.