Capgo Release Workflows
- 421 installs
- 57 repo stars
- Updated July 13, 2026
- cap-go/capgo-skills
capgo-release-workflows is a Capacitor release orchestration skill that coordinates Capgo OTA channels, native CI/CD builds, and app store publishing for developers replacing hosted release services with repo-owned autom
About
capgo-release-workflows is a top-level Capacitor release router from cap-go/capgo-skills that coordinates three workflow areas: Capgo live OTA updates via capgo-live-updates, reproducible native builds via capacitor-ci-cd, and TestFlight or Google Play publishing via capacitor-app-store. It helps teams define Production, Staging, and Dev channel structures, staged rollouts, rollback paths, and signing gates while keeping credentials and release logic in the repository. The skill verifies the full chain—OTA bundle upload, signed native artifacts, and store submission—before broad production traffic. Reach for capgo-release-workflows when migrating Capacitor apps to Capgo OTA plus repo-owned CI/CD instead of a single hosted mobile release platform.
- OTA channel promotion
- Staged rollout automation
- Version and bundle tagging
- Rollback playbooks
- CapGo release pipeline steps
Capgo Release Workflows by the numbers
- 421 all-time installs (skills.sh)
- Ranked #56 of 248 Release Management skills by installs in the Skillselion catalog
- Data as of Aug 1, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cap-go/capgo-skills --skill capgo-release-workflowsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 421 |
|---|---|
| repo stars | ★ 57 |
| Last updated | July 13, 2026 |
| Repository | cap-go/capgo-skills ↗ |
How do you unify Capgo OTA and store releases?
Define CapGo OTA release channels, version promotion, staged rollouts, and rollback steps for Capacitor app updates.
Who is it for?
Capacitor mobile developers adopting Capgo live updates who need one repo-controlled workflow spanning OTA bundles, signed native builds, and app store publishing.
Skip if: Teams building React Native, Flutter, or non-Capacitor apps, or those migrating Ionic Enterprise plugins rather than Capgo OTA, should skip capgo-release-workflows.
When should I use this skill?
User asks to set up Capgo OTA channels, Capacitor CI/CD native builds, staged rollouts, or unified app store publishing with rollback strategy
What you get
Capgo channel plan, CI/CD native build pipeline, store publishing checklist, and rollback verification steps
- OTA channel configuration plan
- CI/CD native build pipeline
- store publishing checklist
By the numbers
- Coordinates 3 workflow areas: live updates, native CI/CD builds, and app store publishing
Files
Capgo Release Workflows
Set up release workflows for Capacitor apps using Capgo live updates plus repository-owned build and publishing automation.
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
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.
Procedures
Step 1: Identify Release Requirements
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.
Step 2: Set Up Live Updates
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.
Step 3: Set Up Native Build Automation
If the team needs reproducible native builds, use the capacitor-ci-cd skill.
Keep signing, build environment variables, and version bumping under repository control.
Step 4: Set Up Store Publishing
If automated publishing is required, use the capacitor-app-store skill.
Keep credentials, track selection, and release gating aligned with the current release policy.
Step 5: Verify the End-to-End Release Flow
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
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.
{
"version": "1.0.0",
"organization": "Capgo",
"date": "March 2026",
"abstract": "Top-level guide for combining Capgo live updates with repository-owned native build and app store publishing workflows.",
"triggers": [
"capgo release workflow",
"capacitor release pipeline",
"live updates builds publishing",
"setup mobile release workflow",
"capgo deployment workflow"
],
"references": [
"https://capgo.app",
"https://capacitorjs.com/docs"
]
}
Related skills
Changelog AutomationAutomatically generate accurate, well-structured changelogs from commit history and Conventional Commits.11.2k38.5k
Msstore CliAutomate publishing, managing submissions, and handling CI/CD for Windows apps in the Microsoft Store.7k37.5k
Changelog GeneratorAutomatically turn git commit history into polished, customer-friendly release notes without manual rewriting.5.9k71.8k
Deploy ChecklistGenerate a complete pre-deployment verification checklist tailored to their service or release.4.6k23.3k
Opensource PipelineSafely strip secrets, sanitize code, and generate required open-source files before releasing a private project publicly.4.3k238k
Community PublishInstantly share running services with public URLs, list projects on a discoverable dashboard, or open-source code to a community GitHub repository.3.9k21How it compares
Pick capgo-release-workflows over capgo-live-updates alone when you need the full Capacitor chain from OTA channels through signed native builds to store publishing.
FAQ
Which sub-skills does capgo-release-workflows coordinate?
capgo-release-workflows coordinates capgo-live-updates for OTA JavaScript bundles, capacitor-ci-cd for signed iOS and Android builds, and capacitor-app-store for TestFlight or Google Play publishing automation.
When should Capacitor developers use capgo-release-workflows?
capgo-release-workflows fits Capacitor teams replacing hosted release services with repo-owned automation that unifies Capgo OTA channels, native artifact builds, and store submission under one verified pipeline.
What rollback steps does capgo-release-workflows emphasize?
capgo-release-workflows requires validating Capgo plugin startup and rollback paths before enabling broad OTA rollout, preserving channel guardrails so a bad JS bundle can revert without a full store resubmission.