A framework upgrade is a controlled engineering change, not simply a Composer update. The goal is to move to a supported version while preserving application behavior.
Establish the baseline
Record the current framework version, PHP runtime, Composer lock file, installed packages and deployment configuration. Run the existing test suite and capture important user journeys before changing dependencies.
Read the upgrade path
Use the official upgrade guide for each relevant major version. Review PHP requirements, removed APIs, changed defaults and package compatibility. Avoid skipping major-version instructions unless the framework explicitly documents a supported path.
Upgrade in a branch
Update constraints deliberately, inspect the lock-file diff and run automated tests. Search application code for deprecated or removed APIs. Upgrade third-party packages only when required and review their own migration notes.
Validate production behavior
Test queue workers, scheduled commands, sessions, cache, mail, file storage and database migrations in staging. Back up data and define a rollback plan before deployment.
Further reading
- Laravel upgrade guide: https://laravel.com/docs/upgrade