Laravel 11 stopped receiving security fixes in March 2026. If a client app is still on it, the upgrade is no longer a "nice to have". The good news: moving from 11 to 12 is one of the gentlest major upgrades Laravel has shipped. Most apps need under a day of work. Here is the checklist I follow on client projects.
1. Check your PHP version first
Laravel 12 needs PHP 8.2 or newer. Run php -v on the server , not just your laptop. Shared hosting and older VPS images often lag behind. Upgrade PHP first, deploy, and confirm nothing breaks before touching Laravel itself.
2. Bump the framework and first-party packages
In composer.json :
"laravel/framework" : "^12.0" , "phpunit/phpunit" : "^11.0" , "pestphp/pest" : "^3.0"
Enter fullscreen mode
Exit fullscreen mode
Then run composer update and read every conflict message. In practice, the blockers are usually third-party packages that haven't tagged a Laravel 12 release yet, not Laravel itself.
3. Carbon 3 is now required
Laravel 12 dropped Carbon 2.…