Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
cap-go avatar

Capacitor App Upgrades

  • 470 installs
  • 57 repo stars
  • Updated July 13, 2026
  • cap-go/capgo-skills

capacitor-app-upgrades is an agent skill that plans and executes Capacitor core version upgrades across iOS, Android, and web targets for developers who need to resolve breaking changes in config, native projects, and bu

About

capacitor-app-upgrades is an agent skill from cap-go/capgo-skills for planning and executing Capacitor framework version bumps across iOS, Android, and web. The skill walks through dependency updates, capacitor.config changes, native project migrations, and plugin compatibility fixes when Capacitor ships breaking API or build-tool changes. Developers reach for capacitor-app-upgrades when a Capacitor major or minor release blocks builds, breaks plugins, or requires native shell edits they cannot safely apply from memory alone.

  • Maps Capacitor breaking changes
  • Updates native project settings
  • Coordinates web and native dependency bumps
  • Validates plugin compatibility matrix
  • Reduces upgrade downtime with ordered steps

Capacitor App Upgrades by the numbers

  • 470 all-time installs (skills.sh)
  • Ranked #309 of 1,039 Mobile Development 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 capacitor-app-upgrades

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs470
repo stars57
Last updatedJuly 13, 2026
Repositorycap-go/capgo-skills

How do you upgrade Capacitor without breaking native builds?

Plan and execute Capacitor core version upgrades across iOS, Android, and web targets while resolving breaking changes in config, native projects, and build scripts.

Who is it for?

Developers maintaining Ionic or Capacitor hybrid apps who must bump @capacitor/core and reconcile iOS, Android, and web breaking changes in one pass.

Skip if: Teams on pure React Native, Flutter, or native-only stacks with no Capacitor dependency should skip capacitor-app-upgrades entirely.

When should I use this skill?

A developer asks to upgrade Capacitor, migrate to a new @capacitor/core major, or fix post-upgrade native build failures on iOS or Android.

What you get

A completed Capacitor version upgrade with updated config files, migrated native iOS and Android projects, resolved plugin conflicts, and passing cross-platform builds.

  • Updated capacitor.config
  • Migrated native iOS and Android projects
  • Resolved plugin compatibility

Files

SKILL.mdMarkdownGitHub ↗

Capacitor App Upgrade

Upgrade a Capacitor app project to a newer major version.

When to Use This Skill

  • User wants to move a Capacitor app from one major version to another
  • User is preparing for a multi-version jump
  • User needs a safe fallback when automated migration does not complete cleanly

Live Project Snapshot

Current Capacitor packages from package.json: !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=[];for(const section of ['dependencies','devDependencies']){for(const [name,version] of Object.entries(pkg[section]||{})){if(name.startsWith('@capacitor/'))out.push(section+'.'+name+'='+version)}}console.log(out.sort().join('\n'))"

Native and Capacitor config paths: !find . -maxdepth 3 \( -name 'capacitor.config.json' -o -name 'capacitor.config.ts' -o -name 'capacitor.config.js' -o -path './ios' -o -path './android' \)

Procedures

Step 1: Detect the Current Version

Start from the injected snapshot above, then confirm @capacitor/core in package.json if anything looks inconsistent.

If the target version is not specified, ask the user to confirm an explicit major version before proceeding.

Step 2: Upgrade One Major Version at a Time

Do not skip intermediate major versions.

For each version jump:

1. Update the @capacitor/* package versions in package.json. 2. Run npm install. 3. Run the Capacitor migration flow if available for that version. 4. Sync native projects with npx cap sync. 5. Verify iOS and Android build cleanly before continuing.

If the automated migration step fails, apply the generated changes manually and continue with the same major version before moving to the next one.

Step 3: Check Native Projects

Review the platform projects for version-specific requirements:

  • iOS deployment target
  • Xcode compatibility
  • Android Gradle Plugin and Java version
  • Any plugin-specific native changes introduced by the new Capacitor major version

Step 4: Final Verification

Run the project checks that matter for the app:

npm install
npx cap sync
npx cap run ios
npx cap run android

If the app has a custom test or build pipeline, run that as well.

Error Handling

  • If the automated migration step only partially completes, finish the current major version manually before trying the next one.
  • If iOS fails, verify the deployment target and Xcode version match the target Capacitor major version.
  • If Android fails, verify the Gradle and Java requirements for the target version.
  • If the app uses plugins with their own upgrade constraints, handle those plugins separately after the app version is stable.

Related skills

How it compares

Pick capacitor-app-upgrades over generic dependency-update skills when Capacitor-specific native project, plugin, and config migrations are required—not just npm version bumps.

FAQ

What does capacitor-app-upgrades change during a Capacitor bump?

capacitor-app-upgrades updates @capacitor/core and related packages, revises capacitor.config, patches iOS and Android native projects, and resolves plugin and build-script breaking changes so hybrid apps compile on all three targets.

When should developers use capacitor-app-upgrades?

capacitor-app-upgrades fits Capacitor or Ionic maintainers hitting failed native builds, deprecated APIs, or incompatible plugins right after a framework release. Use it before shipping a release that depends on a newer Capacitor major.

Mobile Developmentfrontendintegrationsdevops

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.