upgrade

To upgrade an Expo SDK and React Native project, run a guided migration process that assesses your current and target versions, checks dependency compatibility, applies codemods, and verifies builds to ensure configuration changes are applied successfully.

The best way to handle breaking changes during a React Native migration is to use an automated upgrade-assistant that detects issues, generates a dependency compatibility matrix, and applies codemods to fix breaking changes across both Expo managed and bare workflows.

You do not need a separate process; the upgrade-assistant covers both Expo managed and bare workflows. It guides you through the required tooling setup, commands, and configuration changes specific to your workflow to achieve a successful migration.

To verify dependency compatibility before migrating Expo SDK versions, perform a pre-assessment to identify your current and target versions. The upgrade process generates a compatibility matrix to detect potential breaking changes and ensure required tooling is set up correctly.

If builds or tests fail after a React Native upgrade, use the post-upgrade verification steps to identify issues and execute the established rollback plan. This ensures you can safely revert the migration if dependency compatibility or breaking changes cause failures.