capacitor-app-upgrades

To upgrade a Capacitor app, you can use automated CLI migration alongside manual fallbacks for dependency updates and iOS/Android project changes. The process enforces sequential, version-guarded steps to safely move between major releases.

Yes, multi-version jumps are supported when upgrading a Capacitor app. The process enforces a sequential upgrade path, guiding you through each intermediate major version step-by-step to ensure all project changes are applied correctly.

Manual steps for a Capacitor upgrade involve applying project-specific changes for Android and iOS that the automated CLI cannot handle. Dedicated reference docs provide version-specific fallback guidance for dependencies and native project configurations.

Yes, the Capacitor upgrade process fully supports both Android and iOS projects. It covers platform-specific dependency updates, native project changes, and post-upgrade verification to ensure both environments are successfully migrated.

If the automated Capacitor CLI migration fails, you should use the provided manual fallback guidance. The skill includes error handling guidance and structured references for each version transition to complete the upgrade manually.

No, this tool is strictly for major-version upgrades of the Capacitor framework itself, such as 5 to 6 or 7 to 8. It should not be used for plugin library upgrades or non-Capacitor mobile frameworks.