Laravel 10

Laravel 10 raised the minimum PHP version to PHP 8.1, so applications and deployment environments that remained on PHP 8.0 could not move to this line. It updated core dependencies, including the Symfony component set, and expanded native PHP type declarations across the framework and application skeleton. Those types improve static analysis and editor support, but custom classes that extend framework classes or implement Laravel contracts may need signature changes to remain compatible. Laravel 10 also moved validation rules toward the ValidationRule contract, replacing the older invokable-rule approach for newly written rules.

Laravel 10 has reached end of life. Existing applications can continue to run, but Laravel no longer provides fixes for security issues or defects in this framework line. The practical exposure is not limited to a newly discovered framework vulnerability: unsupported transitive dependencies, PHP runtime upgrades, and package-maintainer support policies can increasingly make a Laravel 10 deployment harder to patch, test, or reproduce. Delaying the move also increases migration scope, because application code, custom framework extensions, Composer packages, and operational tooling drift further from supported Laravel and PHP versions.

Plan an upgrade to a currently supported Laravel release, following the official upgrade guidance for every major version crossed rather than treating the change as a single dependency update. First inventory the deployed PHP version, Composer packages, custom service providers, middleware, authentication code, queue jobs, validation rules, and classes that extend or implement Laravel framework types. Build the upgrade in a separate branch and environment, update PHP and Composer constraints, resolve package compatibility, and address signature or deprecation changes before deploying. Run automated tests plus focused checks of authentication, authorization, validation, database migrations, queues, scheduled commands, cache and session drivers, mail, filesystem storage, and external integrations. Deploy through a staged rollout with rollback capability, then keep the application on a supported Laravel and PHP maintenance path.