Ionic and Capacitor Upgrade Resilience During Major Version Jumps

Ionic/Capacitor Integration Boundary

The goal is to ensure application stability when migrating Ionic applications across major framework versions while maintaining native plugin functionality.

Constraint Uncertainty

The resilience of the integration boundary is uncertain because rollback is managed externally, not by the Ionic framework itself.

When performing a major Ionic version upgrade, what specific lifecycle hooks within Capacitor must be verified for backward compatibility? Does Ionic documentation specify any required pre-upgrade checks for native plugin state preservation?