Framework end-of-life calendar
The day each version stops receiving fixes, earliest first. Every date links to the project's own page.
| Version | Support ends | Status on 26 October 2026 |
|---|---|---|
| 12 March 2026 | Ended | |
| 30 April 2026 | Ended | |
| 1 October 2026 | Ended | |
| 10 November 2026 | Ends within a year | |
| 10 November 2026 | Ends within a year | |
| 28 November 2026 | Ends within a year | |
| 24 February 2027 | Ends within a year | |
| 30 April 2027 | Ends within a year | |
| June 2027 | Ends within a year | |
| October 2027 | More than a year away | |
| 17 March 2028 | More than a year away | |
| 30 April 2028 | More than a year away | |
| June 2028 | More than a year away | |
| October 2028 | More than a year away | |
| 14 November 2028 | More than a year away |
You ticked . Ended: . Ending within a year: .
Your ticks stay on this page: they are not sent anywhere or saved.
For Angular the date is the end of long-term support. For Laravel it is the end of security fixes; bug fixes stop earlier. For the others it is the date the project gives as end of life or end of support.
Dates as each project's page stated them on 18 October 2026. The linked page is always the authority.
Where to go from here
The use case for a version that has reached its end:
Move off an ageing framework without stopping the product
What end of life means for security fixes and hiring: A framework end-of-life calendar for product leaders
The next guide: EU rules calendar
Lift your eyes and let us carry the rest.
Talk to us and see what carrying your product forward looks like.
Prefer to write directly? contact@zefana.com