Upgrades · 2026-11-12 · 4 min read
What actually breaks when a Laravel app passes end of support
The failures are rarely dramatic. They arrive as a package that will not update, a payment library that drops your version, and a security review you cannot pass.
Mohit Tanwani
Founder, Tech Mitrise
The short version
Laravel and Yii don't stop working the day they pass end of support — they stop receiving security fixes, which means every dependency, host and compliance review built around 'patched within N days' quietly breaks instead. The practical sequence is: confirm your exact version's real end date, check which of your dependencies already dropped support for it, then upgrade in the smallest safe steps rather than jumping straight to the newest release.
"End of support" doesn't mean the app stops running
Nothing crashes on the end-of-support date. Laravel 10 reaching its end date, for instance, didn't take any running application down — the code kept executing exactly as it had the day before. What actually happens is quieter and more dangerous: the framework stops receiving security fixes, and everything that assumed "running a supported version" as a precondition starts failing on its own schedule, not yours.
In practice, three things break first, in roughly this order:
- A dependency drops support first. Package maintainers set their own minimum supported framework version, often tied to the framework's own support window. A payment SDK, a PDF library, or an auth package pushes a major version that simply won't install alongside your now-unsupported Laravel or Yii version —
composer updatestarts failing with a version conflict, not a warning. - A compliance or security review fails. SOC 2, PCI, or a customer's own vendor-security questionnaire routinely asks "are you running a supported, patched version of your framework and language runtime." An unsupported version is an automatic fail on that line, independent of whether anything has actually gone wrong yet.
- A real vulnerability goes unpatched. This is the slow one. A CVE affecting your exact version is found after end of support, and because the framework no longer backports security fixes to it, the fix only exists in a version you'd have to upgrade into anyway — under time pressure, instead of on your own schedule.
How to check your own system
Three checks, in order of how fast they give you an answer:
- Confirm your exact version against the official source, not a general "is Laravel X EOL" search result. Laravel and Yii both publish their own release/support tables, and Yii in particular has two separate support tracks (Yii 1.1 and Yii 2.x) with different end dates — see the end-of-support calendar for the verified date for each specific version, each linked to its own official source.
- Check your actual dependency tree for version floors, not just your framework version:
composer outdated --direct
composer why-not laravel/framework ^12.0
- Check whether your hosting or PHP version is itself approaching its own end date — a framework upgrade and a PHP version upgrade are often forced together, and PHP's own supported-versions page (php.net) is the authority on that date, not your framework's docs.
Not sure where your system stands?
A 20-minute call with the founder will tell you whether this applies to you and what to do first.
What to do first
The instinct is to jump straight to the newest major version. That's usually the wrong first move on a production system with no recent upgrade history — each major version can carry its own breaking changes, and skipping several at once compounds them into one large, hard-to-debug jump.
The practical sequence: upgrade one major version at a time, running the existing test suite (or writing the minimum tests needed to cover your critical paths first, if there isn't one) between each step, rather than jumping straight to current. Check each intermediate version's own upgrade guide for breaking changes specific to that step — Laravel and Yii both publish one. This takes longer than a single jump, but each step is independently verifiable, and a failure at any step tells you exactly which version boundary caused it.
If you're not sure where your own system actually stands against its real end-of-support date, the end-of-support calendar has the verified date for every version we track, or a Critical Software X-Ray will tell you specifically what's at risk in your system.

Written by Mohit Tanwani
Founder of Tech Mitrise. He does the rescue and upgrade work described here. 10+ years building, running and repairing production Laravel, Yii and PHP systems.
About the founderSources: laravel.com/docs/releases, yiiframework.com/release-cycle, php.net/supported-versions.php — every date below is linked to its official source on the end-of-support calendar. Last checked 12 Nov 2026.
