Laravel package compatibility matrix

Every package we track has a release line that allows Laravel 13. If Composer refuses, the likely reason is that you’re on an older line of a package, or a plugin is holding it back. It’s rarely that the package has no route forward.

11 release lines stop at Laravel 12. These are the ones that block the step to 13 until you change major version of the package itself:

• inertiajs/inertia-laravel v1.3.4: move to v2.0.28 (PHP ^8.1.0)
• backpack/crud 6.8.17: move to 7.1.22
• yajra/laravel-datatables-oracle v12.7.2: move to v13.3.1 (PHP ^8.3)
• laravel/passport v12.4.3: move to v13.10.0 (PHP ^8.2)
• laravel/cashier-paddle v1.12.0: move to v2.8.1 (PHP ^8.1)
• spatie/laravel-backup 9.4.1: move to 10.3.3 (PHP ^8.3)
• laravel/boost v1.8.13: move to v2.10.4 (PHP ^8.2)
• statamic/cms v5.74.7: move to v6.39.0
• pestphp/pest-plugin-laravel v3.2.0: move to v4.1.0 (PHP ^8.3.0)
• barryvdh/laravel-debugbar v3.16.5: move to v4.4.5 (PHP ^8.2)
• laravel/tinker v2.11.1: move to v3.0.2 (PHP ^8.1)

PHP 8.4 floors have started to appear. Laravel 13 supports PHP 8.3–8.5, but these lines won’t install on PHP 8.3: spatie/laravel-activitylog 5.1.3, spatie/laravel-query-builder 7.3.7, spatie/laravel-translatable 6.15.0, pestphp/pest-plugin-laravel v5.0.1. An older line of each still works on 8.3, so this limits how far you can update, not whether you can run the package. It’s still a reason to prefer PHP 8.4 when you next move.

Some packages now follow the framework one for one. The newest lines of yajra/laravel-datatables-oracle each allow a single Laravel major, so that package has to move in the same pull request as the framework. For most others you can update the package first and release it separately, which makes any fault easier to trace.

Filament

Filament 3 installs on Laravel 13, which surprises people who assume they must move to Filament 5 first. You can upgrade the framework, release, and then take Filament’s own majors separately. Filament 2 can’t do this, as it stops at Laravel 10. Our Filament upgrade path covers the order.

Livewire

Livewire 3 and 4 both allow Laravel 10 to 13 and PHP 8.1 or later. Livewire 2 stops at Laravel 10. Filament ties you to a line: Filament 4 requires Livewire 3, and Filament 5 requires Livewire 4.

Inertia

The server adapter inertiajs/inertia-laravel version 1 stops at Laravel 12, and its PHP constraint ends at 8.4, so it’s out of the question on PHP 8.5. Version 2 reaches Laravel 13 from Laravel 10. Version 3 needs Laravel 11.35 and PHP 8.2. Remember the client adapter moves with it, so budget for front-end changes too.

Nova and Spark

Both are private packages, so Packagist has no public record of them. Nova’s installation page lists Laravel 10.x to 13.x for Nova 5. Spark’s release notes have entries reading “Supports Laravel 13”. That’s all we could confirm from public sources. For the exact constraint, check the composer.lock of a licensed install.

Passport and Sanctum

Passport 12 stops at Laravel 12, so the move to Passport 13 is part of reaching Laravel 13, and it needs Laravel 11.35 and PHP 8.2. Sanctum 4 allows Laravel 11 to 13. Check Passport’s own upgrade guide before you plan this step, because token and grant behaviour is what API clients notice first.

Spatie packages

Several Spatie packages have recently dropped older Laravel versions in their newest majors. For example, spatie/laravel-permission 7 and 8 need Laravel 12 and PHP 8.3, while version 6 still reaches back to Laravel 8 and forward to 13. On Laravel 13 you can stay on the older line while you plan the major update.

Testing tools

These get forgotten until the framework step fails. pestphp/pest-plugin-laravel 5 allows Laravel 13.23 or later only, with PHP 8.4. Version 4 is the line to use on PHP 8.3. Move your test tooling in the same branch as the framework, or you lose the safety net when you need it most.

Composer constraints look cryptic, but only a few forms appear in this table.

• ^12.0 means any 12.x release from 12.0 up, and not 13. The caret stops at the next major version, which is why a package has to declare each new Laravel major before Composer will accept it.
• ^10.45|^11.0 means either range is fine. The double form, ||, means the same thing.
• ^12.40.0 has a minor floor. It allows Laravel 12, but only from 12.40. If you’re on an earlier 12.x, run composer update laravel/framework first. This is a cheap fix, and it’s easy to mistake it for a real block.
• ~8.4.0 means 8.4.x only. In the PHP column, a list ending in that form is a true ceiling, and it’s the only way a package here says it won’t run on a newer PHP.

There’s one more thing to watch for when a row looks fine but Composer still refuses. A package can require illuminate/* components at a version that your other packages disagree with, or need a dependency such as Livewire at a higher major than you have. So read Composer’s full explanation, not only its last line. The real cause is often two levels down from the package it first names.

We’d use this table to split a large upgrade into smaller releases. Each stage below can go live on its own, which means any fault points to one change.

1. Update what allows both versions. Find the rows that allow your current Laravel and your target. Move to those lines first, while the framework stays where it is. Horizon, Telescope, Socialite and Scout usually belong here, because a single line covers several Laravel majors.
2. Sort out PHP. Pick a version your target Laravel and all your target package lines accept, and release it alone. Use the PHP column above, then our guide to choosing a PHP version.
3. Move what must change with the framework. Packages with no shared line, such as yajra/laravel-datatables-oracle, go in the same pull request as Laravel. Keep this list as short as you can, as it’s where failures are hardest to untangle.
4. Take the big package majors afterwards. If a line such as Filament 3 still allows your target, leave its major upgrade for a later project. Your deadline is usually about framework support, not about being on the newest admin panel.

A table can’t see your lock file, and these commands can. Run them on a branch.

• composer why-not laravel/framework ^13.0 names each package blocking Laravel 13.
• composer why-not php 8.4 does the same for a PHP version.
• composer outdated --direct shows how far behind your own requirements are.
• composer audit lists known security advisories against what you have installed.

Private and in-house packages won’t appear here, and they’re often the real blocker. Include them in your own list. A paid package may also need a licence renewal before you can reach a newer major, so check that early. Our upgrade checklist places these checks in the full sequence.

A script reads each package’s public metadata from Packagist’s repository API, skips development, alpha, beta and release-candidate versions, and keeps the newest release in each major. It then records the release’s PHP requirement and its requirement on laravel/framework or, where the package doesn’t require the framework directly, on illuminate/support, illuminate/contracts or a similar component. For Filament, the constraint sits on filament/support, so we read it from there at the matching version.

We wrote the short notes by hand. The package list is our own choice of widely used packages and doesn’t claim to be complete or a popularity ranking. “Not declared” means the release has no direct PHP requirement of its own, so it inherits one from its dependencies.

• Whether it works. Maintainers can allow a Laravel version before every feature has been exercised on it, and a constraint can’t describe how your code uses the package. We haven’t tested every combination here.
• Upper limits on PHP. Most packages use open-ended PHP constraints such as ^8.2, which Composer will accept on PHP 8.5 whether or not the maintainer has tried it. Read a deprecation log before you trust a new PHP version. See what PHP 8.5 changes for Laravel.
• Minor floors. “Allows Laravel” shows majors. A row can need a recent minor, such as 11.28 or 12.40, so read the constraint beside it if you’re not on a recent release.
• Support. A line that allows your Laravel version may no longer get fixes. The release date under each version gives a rough idea of activity, and Packagist’s abandoned flag shows in the notes when a package carries it. None of the lines above does as of the last check.

For which PHP goes with which framework version, use our Laravel and PHP compatibility matrix. For release and support dates, see Laravel versions. If the blockers above look like more work than your team has room for, our Laravel upgrade service begins with a free assessment of your code. Published prices run $799–$2,999+ in USD, invoiced in USD, GBP, EUR or INR.