Upgrades and deprecations
Upgrade Laravel 9 to the Latest Version: Hop Order, PHP and Dates
In short
Go one major at a time: 9, then 10, 11, 12 and 13, because each official upgrade guide covers a single step. Laravel 13 (released 17 March 2026) is the current release and needs PHP 8.3 or newer. Laravel 9 has had no security fixes since 6 February 2024, and Laravel 12 loses them on 24 February 2027.
Where does each Laravel version stand on 19 November 2026?
Laravel's support policy gives every release 18 months of bug fixes and 2 years of security fixes. Measured against that policy, only Laravel 12 and 13 are still supported, and Laravel 12 is already in its security-only window.
That makes the start and the end of the route different problems. Laravel 9 is almost three years past its security end date. Laravel 12 looks safe, but it has only about three months of security fixes left.
| Version | PHP range stated by Laravel | Security fixes until | Status on 19 Nov 2026 |
|---|---|---|---|
| 9 | 8.0 - 8.2 | 6 February 2024 | Ended |
| 10 | 8.1 - 8.3 | 4 February 2025 | Ended |
| 11 | 8.2 - 8.4 | 12 March 2026 | Ended |
| 12 | 8.2 - 8.5 | 24 February 2027 | Security fixes only (bug fixes ended 13 August 2026) |
| 13 | 8.3 - 8.5 | 17 March 2028 | Current (bug fixes until Q3 2027) |
In what order should the hops go?
Laravel publishes one upgrade guide per major, and each is titled as a single step, such as "Upgrading To 13.0 From 12.x". I found no official guide that covers a multi-version jump. I would therefore treat the route as four separate releases, each one deployed and tested before the next starts.
- 9 to 10: the 10.x guide estimates 10 minutes. It requires PHP 8.1.0 and Composer 2.2.0, and moves
minimum-stabilitytostable. - 10 to 11: the 11.x guide estimates 15 minutes. It requires PHP 8.2.0 and has six high-impact items, the most of any hop.
- 11 to 12: the 12.x guide estimates 5 minutes. Its high-impact items are the dependency bumps and the installer update.
- 12 to 13: the 13.x guide estimates 10 minutes. It adds the
PreventRequestForgerymiddleware rename to the high-impact list.
Which PHP version does each hop need?
The PHP floor rises at three of the four hops, and the numbers are the part of the route people trip over. The table below joins the requirement lines from the four guides and the release notes.
| Hop | PHP requirement in Laravel's docs | Other stated requirement |
|---|---|---|
| 9 to 10 | PHP 8.1.0 or greater | Composer 2.2.0 or greater |
| 10 to 11 | PHP 8.2.0 or greater | curl 7.34.0 or greater; SQLite 3.26.0 or greater if used |
| 11 to 12 | 8.2 - 8.5 in the support table; the 12.x guide lists no new PHP floor | Carbon 3 is required |
| 12 to 13 | PHP 8.3 minimum | Dependency bumps for Boost, Tinker, PHPUnit and Pest |
Checked against: source 1, source 3, source 4, source 5, source 6
Can one PHP upgrade carry the whole climb?
Almost. PHP 8.2 sits inside the stated range for Laravel 9, 10, 11 and 12, so a single PHP move to 8.2 can come before the first hop. The catch is on php.net: its supported-versions page lists 8.2 security support as ending on 31 December 2026.
I would plan it like this. Move PHP to 8.2 while still on Laravel 9, make the hop to 10, then move PHP to 8.3 on Laravel 10, which accepts it. Hops 11, 12 and 13 then run on a PHP that is already supported and the last hop needs no PHP change.
The php.net page I fetched lists only 8.2 to 8.5 as supported and gives no end dates for 8.0 or 8.1. If Composer refuses an install during any hop, this fix page explains which PHP it is checking.
Which hop is the heavy one?
By the guides' own impact lists it is 10 to 11. Laravel 11 introduced a new default application structure, but the guide does not recommend that upgrading apps migrate to it, because Laravel 11 still supports the Laravel 10 structure.
The costly items sit in the database layer. Migrations that use change() must now repeat every modifier you want to keep, or the column loses them. The double and float column types were rewritten, and the Sanctum 4 and Passport 12 packages no longer load their own migrations. If you have many old change() migrations, the guide suggests squashing them with this command.
php artisan schema:dumpChecked against: source 4
Where should the route stop, and what do the docs leave out?
I would plan to land on 13, not 12. Laravel 12 has no bug fixes now and about three months of security fixes. Stopping there only schedules another hop for early 2027.
The guides cover the framework and Laravel's first-party packages. The 10.x guide tells you to check every third-party package for a release that supports the new version, and that work is not described anywhere in the framework docs. The 13.x guide also names Laravel Shift, a community-maintained service, and Laravel Boost, whose upgrade command needs an existing Laravel 12 app.
This page compares vendor documents. It does not cover your own code, test coverage or deployment steps.
What else do people ask?
Can I jump from Laravel 9 straight to 13?
The official guides each start from the previous major, and I found no guide for a multi-version jump. Treat each major as its own step.
Does Laravel 12 still get fixes?
Security fixes only. Its bug-fix window ended on 13 August 2026 and security fixes run until 24 February 2027.
Sources
- Laravel 13.x release notes, support policy and PHP table, fetched 2026-11-19
- Laravel 9.x release notes, support policy table, fetched 2026-11-19
- Laravel 10.x upgrade guide, 9.x to 10.0, fetched 2026-11-19
- Laravel 11.x upgrade guide, 10.x to 11.0, fetched 2026-11-19
- Laravel 12.x upgrade guide, 11.x to 12.0, fetched 2026-11-19
- Laravel 13.x upgrade guide, 12.x to 13.0, fetched 2026-11-19
- PHP supported versions, php.net, fetched 2026-11-19
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. This page compares vendor documents I fetched on 19 Nov 2026 (the Laravel release notes and upgrade guides, and php.net). I did not run these upgrades for it. It does not cover third-party packages, your test suite or production rollout. Found a mistake? Tell me.