laravel end of life dates — full support timeline
8 of 10 tracked laravel releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 13 | 2026-03-17 | 2028-03-17 | 13.23.0 | supported |
| 12 | 2025-02-24 | 2027-02-24 | 12.64.0 | supported |
| 11 | 2024-03-12 | 2026-03-12 | 11.55.0 | ended |
| 10 | 2023-02-14 | 2025-02-04 | 10.50.2 | ended |
| 9 | 2022-02-08 | 2024-02-06 | 9.52.21 | ended |
| 8 | 2020-09-08 | 2023-01-24 | 8.83.29 | ended |
| 7 | 2020-03-03 | 2021-03-03 | 7.30.7 | ended |
| 6 LTS | 2019-09-03 | 2022-09-06 | 6.20.45 | ended |
| 5.8 | 2019-02-26 | 2020-02-26 | 5.8.38 | ended |
| 5.5 LTS | 2017-08-30 | 2020-08-30 | 5.5.50 | ended |
Who is affected
Anyone running an unsupported laravel release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.
Source
These dates are maintained by endoflife.date/laravel, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next laravel deadline
You are reading this because a laravel release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every laravel and related deadline as it is announced, with exact dates and primary sources.
Watch laravel deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.