Blog
Upgrade Routes and Deprecated Packages
The order to upgrade an old framework in, the runtime each step needs, the dates that matter, and what to use when a package you depend on is deprecated.
Old frameworks and runtimes rarely fail all at once. They fall out of support on a date, and the real work is the order of the upgrade: which versions to hop through, which runtime version each hop needs, and what the official guides leave to you. The notes here lay out those routes for Laravel, Spring Boot, Django, PHP and Node, and say what to use when a long-trusted package is deprecated.
Dates and version ranges come from the official release pages and upgrade guides, fetched on the date shown under each page's Sources. These are plans read from documents. They do not cover your own code, your test coverage or your rollout, and where the documentation is silent the page says so instead of guessing.
Upgrade routes
2026-11-19
Upgrade Spring Boot 2.7 to the Latest Version: Java, Jakarta and Hop Order
Move to Java 17, then go 2.7 to 3.x with the 3.0 migration guide, reach the latest 3.5.x, and only then take the 4.0 guide to 4.1, the current release (4.1.2). The javax to jakarta rename happens once, at 3.0. The Java 17 floor is the same on 3.0, 4.0 and 4.1.
Read2026-11-19
Upgrade PHP 7.4 to 8.x: Hop Order, Dates and Blockers
PHP 7.4 reached end of life on 28 November 2022, and 8.0 and 8.1 are unsupported too. php.net supports 8.2, 8.3, 8.4 and 8.5 today. The manual has one guide per step, so the route is 8.0, 8.1, 8.2, 8.3, then 8.4 or 8.5. I would aim for 8.4 or 8.5 because 8.2 loses security fixes on 31 December 2026.
Read2026-11-19
Upgrade Node 18 to the Latest LTS: Hop Order and Dates
The official schedule gives Node.js 18 an end of life of 30 April 2025. The lines in LTS today are 22, 24 and 26, and 26 is the newest. The route is 20, 22, 24, then 26, reading each major's changelog on the way. I would aim for 24 or 26, because 22 itself ends on 30 April 2027.
Read2026-11-19
Upgrade Laravel 9 to the Latest Version: Hop Order, PHP and Dates
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.
Read2026-11-19
Upgrade Django 3.2 to the Latest LTS: Route, Python and Dates
Take Django 3.2 to 4.2 and then to 5.2, one LTS at a time. Django 5.2 is the newest released LTS and gets security fixes until April 2028. Django 4.2 lost its extended support on 7 April 2026, so it is a stop on the way, not a destination. The next LTS, 6.2, is planned for April 2027.
ReadNext step
Have a project in mind?
Tell me about it. A discovery call within 48 hours.