Symfony and Zend

Symfony, Zend and Laminas apps on supported versions again.

PHP 8.2 gets no security fixes after 31 December 2026, and Symfony 6.4 stops getting bug fixes in November 2026. We move Symfony, Zend Framework and Laminas applications to supported versions and PHP 8.4, with tests in place first and one fixed price.

Upgrades from €3,000. Free first look: we reply with the first step and its fixed price.

Why now

  1. PHP 8.2 support runs out

    No security fixes from php.net after 31 December 2026.

  2. Symfony 6.4 moves to security fixes only

    Bug fixes end in November 2026, security fixes in November 2027.

  3. Zend Framework 1 has long been unsupported

    Its support ended on 28 September 2016. The community fork zf1-future keeps it running; its maintainers list PHP 8.2 as the newest tested version.

  4. Laminas MVC is winding down

    Security fixes only until 31 December 2028, and no PHP 8.5 support.

The dates that matter

As of 1 November 2026, from php.net, symfony.com, getlaminas.org and framework.zend.com. All dates with sources: EOL calendar.
VersionWhat endsWhen
PHP 8.2security fixes31 December 2026
Symfony 6.4 LTSbug fixesNovember 2026
Symfony 5.4 LTSsecurity fixes (extended)February 2029
Laminas MVCsecurity fixes31 December 2028
Zend Framework 1all fixes (ended)28 September 2016

Typical paths

FromToHow
Symfony 3–7.3Symfony 7.4 LTSDeprecation log cleared first, then one LTS at a time (6.4 as a stepping stone).
Symfony 8.0current Symfony 8Symfony 8.0 has had no fixes since July 2026. The step to a newer 8.x is a minor upgrade.
Zend Framework 1zf1-future on a newer PHP, or a staged move to Symfonyzf1-future is tested up to PHP 8.2, whose security support ends on 31 December 2026. A staged move is often the safer path.
Laminas MVCMezzio or SymfonyThe Laminas project recommends Mezzio; a move to Symfony fits when the rest of your stack is Symfony.
PHP 7.x, 8.0–8.2PHP 8.4 or 8.5Rector for the mechanical changes, PHPStan to find what is left, an engineer for the rest.

How it runs

  1. 01

    Code Audit

    We measure the gap: PHPStan, a Rector dry run, the Symfony deprecation log, composer outdated and composer audit, plus a read-through of the code.

  2. 02

    Fixed price

    You get the scope, the steps, the schedule and one price before we start.

  3. 03

    Tests first

    Characterization tests on the critical paths, and CI that runs them on every change.

  4. 04

    One version at a time

    Each step is a merge request you can review. The details: how an upgrade runs.

Symfony and Zend questions

Can we stay on Symfony 5.4?

For a while. Symfony 5.4 security fixes run until February 2029, but its bug fixes ended in November 2024. Plan the move to 7.4 LTS before it becomes urgent.

Zend Framework 1: upgrade or rewrite?

Usually neither in one go. zf1-future gets the app onto a newer PHP quickly, and a staged move to Symfony replaces it part by part while the app keeps running. See Modernization.

PHP 8.4 or PHP 8.5?

PHP 8.5 gets security fixes until 31 December 2029, PHP 8.4 until 31 December 2028. We usually recommend the newest version that all your dependencies support.

Our Symfony app was built by someone else. Is that a problem?

No, most of our work is exactly that. When nobody knows the app anymore, a Takeover comes first.

Find out what your upgrade involves

Send us your composer.json and your PHP version. Free first look: we reply with the first step and its fixed price.