cap-go/capgo-skills/capacitor-ci-cd

CI/CD for Capacitor Apps

Build, sign, and ship Capacitor apps from CI with the right toolchain for the Capacitor major in use.

When to Use

TRIGGER when:

• Creating or fixing .github/workflows/*.yml, .gitlab-ci.yml, fastlane/Fastfile, or a Capgo Cloud Build job.
• Picking runner images, Node/Xcode/JDK versions for Capacitor 8 or 9.
• Automating signing, TestFlight/Play uploads, version bumps, or Capgo OTA uploads.
• A CI build fails while a local build works.

Do not use for:

• Manual submission, listing, screenshots -> capacitor-app-store.
• Capgo Cloud Build credential setup and troubleshooting -> capgo-native-builds.
• Channel promotion, staged OTA rollouts -> capgo-release-workflows.
• Writing unit/E2E tests -> capacitor-testing.
• Security scanning rules -> capacitor-security.

Live Project Snapshot

Capacitor version, Node engine, and scripts: !node -e "const fs=require('fs');if(!fs.existsSync('package.json'))process.exit(0);const pkg=JSON.parse(fs.readFileSync('package.json','utf8'));const out=[];if(pkg.engines)out.push('engines='+JSON.stringify(pkg.engines));if(pkg.packageManager)out.push('packageManager='+pkg.packageManager);for(const section of ['dependencies','devDependencies']){for(const [name,version] of Object.entries(pkg[section]||{})){if(name.startsWith('@capacitor/')||name==='@capgo/cli'||name==='@capgo/capacitor-updater')out.push(section+'.'+name+'='+version)}}for(const [name,cmd] of Object.entries(pkg.scripts||{})){if(/build|test|lint|sync|release/i.test(name))out.push('scripts.'+name+'='+cmd)}console.log(out.join('\n'))"

Existing CI, lockfiles, and native build files: !find . -maxdepth 4 -not -path '*/node_modules/*' \( -path './.github/workflows/*' -o -name '.gitlab-ci.yml' -o -name 'Fastfile' -o -name 'Appfile' -o -name 'Matchfile' -o -name 'ExportOptions.plist' -o -name 'Podfile' -o -name 'Package.swift' -o -name 'gradle-wrapper.properties' -o -name 'variables.gradle' -o -name '.nvmrc' -o -name '.node-version' -o -name 'bun.lock' -o -name 'package-lock.json' -o -name 'pnpm-lock.yaml' -o -name 'yarn.lock' \)

Toolchain Matrix

Store-side deadlines: Apple requires the iOS 26 SDK now and the iOS 27 SDK from April 2027; Google Play requires target API 36 since Aug 31, 2026. A Capacitor 8 app on macos-26 meets both today.

Pin Xcode explicitly when several are installed: sudo xcode-select -s /Applications/Xcode_<version>.app (exact folder names are listed in the runner image README).

Choose a Pipeline Shape

Ask the user when unclear:

1. Capgo Cloud Build - no macOS runner or local signing setup; any Linux runner calls npx @capgo/cli@latest build request <appId> --platform ios|android. Credentials are saved once with npx @capgo/cli@latest build credentials save ... (or build init for guided iOS setup) and passed in CI as env vars. Load capgo-native-builds for details.
2. Self-hosted GitHub Actions / GitLab - full control; you manage macOS runners, certificates, and keystores. See references/github-actions.md, references/gitlab-ci.md.
3. Fastlane inside either - best when match/pilot/supply are already in use. See references/fastlane.md.

Web-only changes after a native release can skip native builds entirely: upload a Capgo bundle (npx @capgo/cli@latest bundle upload --channel <channel>, auth via CAPGO_TOKEN). Native changes (plugins, permissions, Capacitor upgrades) always need a native build.

Procedure

1. Read the snapshot: Capacitor major, package manager + lockfile, iOS dependency manager (Package.swift -> SPM, Podfile -> CocoaPods), existing workflows.
2. Pick toolchain versions from the matrix. Set Node from .nvmrc/engines if present.
3. Structure jobs: test (lint, typecheck, unit) -> build-web (artifact <webDir>) -> ios + android in parallel -> deploy jobs gated on branch/tag. Always run npx cap sync <platform> on the native job after restoring the web artifact; never commit synced assets as a CI shortcut.
4. Signing: follow references/signing-and-secrets.md. Prefer App Store Connect API keys over Apple ID passwords; keep Android keystore and passwords in secrets, decode at runtime, delete after.
5. Build numbers: derive from CI (GITHUB_RUN_NUMBER, CI_PIPELINE_IID) or let Capgo Cloud Build bump them. Never reuse a build number.
6. Add caching (references/caching-and-versioning.md).
7. Run the pipeline on a branch first, uploading to TestFlight internal / Play internal track only.

Verification

• The workflow passes on a clean runner twice in a row (cache cold and warm).
• Logs show the expected tool versions: add node -v, xcodebuild -version, java -version, ./gradlew --version steps.
• iOS artifact: unzip -l App.ipa | grep Payload/App.app and the build appears in TestFlight with the expected build number.
• Android artifact: bundletool dump manifest --bundle app-release.aab | grep -E "versionCode|targetSdkVersion" matches expectations; build appears in the Play internal track.
• Capgo: npx @capgo/cli@latest bundle list shows the uploaded version on the intended channel.
• No secret values printed in logs (GitHub masks registered secrets; never echo decoded files).

Error Handling

References

• references/github-actions.md - complete workflow: test, web build, iOS (SPM/CocoaPods), Android, Capgo OTA, Capgo Cloud Build job.
• references/gitlab-ci.md - GitLab pipeline with macOS runner tags.
• references/fastlane.md - iOS and Android lanes with API keys and match.
• references/signing-and-secrets.md - certificate/profile import, API key auth, Android keystore wiring, secret inventory.
• references/caching-and-versioning.md - npm/Gradle/SPM/CocoaPods caches, build numbers, semantic-release.