Laravel 13

Laravel 13 is the major framework line following Laravel 12. The supplied cycle data confirms that it is currently supported, but it does not identify the release-note changes, platform requirements, or removed APIs for this line. It would be inaccurate to claim specific new features or breaking changes without checking Laravel’s Laravel 13 release notes and upgrade guide. Plan the move from Laravel 12 as a major-version upgrade: verify the required PHP and Composer constraints, then assess application code and every installed Laravel package against the documented upgrade changes.

Remaining on Laravel 13 does not, by itself, put the application on an unsupported framework line. The principal risk is deferring work until the gap to a later Laravel line includes several framework, PHP, Composer, and ecosystem changes at once. Applications with limited automated coverage, unmaintained packages, direct use of framework internals, custom authentication or queue integrations, or tightly coupled front-end tooling are more likely to encounter expensive upgrade work. The practical cost is therefore ongoing compatibility assessment and a potentially larger future migration, rather than an immediate loss of framework coverage.

Record the application’s current PHP version, Laravel version, Composer lockfile, first-party Laravel packages, third-party packages, deployment image, queue workers, scheduler, and front-end build tooling. Establish passing automated tests around login, authorization, database writes, jobs, events, mail, file storage, payments, and critical user flows before changing dependencies. Select the intended later Laravel target, read its official upgrade guide alongside the upgrade guides for each intervening major line, and identify required PHP and package upgrades. Perform the Composer update in a separate branch, resolve deprecations and compatibility issues, run static analysis and the full test suite, then deploy through a non-production environment with production-like queues, cache, session, and storage settings. Keep Laravel 13 patched while the migration work is underway.