Symfony 7.4

7.4 released 27 November 2025, latest 7.4.16.

Symfony 7.4 is currently supported. Active support is scheduled to end on 30 November 2028. It reaches end of life on 30 November 2029.

What changed

Symfony 7.4 is the long-term-support minor line in the Symfony 7 generation. It keeps the Symfony 7 platform baseline, including the PHP 8.2 minimum, while collecting the framework, component, tooling, and developer-experience additions made since Symfony 7.3. For an application already on Symfony 7.3, the upgrade is a minor-version upgrade: existing public APIs remain available under Symfony’s compatibility policy, but newly introduced deprecations should be treated as preparation work for a later major upgrade. It is not a rewrite of the Symfony 7 architecture.

What staying costs

Remaining on Symfony 7.4 carries low immediate lifecycle risk while the line is supported and receiving applicable maintenance and security fixes. The trade-off is that an application will not gain capabilities, integrations, runtime improvements, or dependency compatibility introduced only in newer Symfony lines. The larger practical risk is deferring deprecation cleanup: dependencies and application code can accumulate compatibility work, making a later major-version move broader and harder to test. Symfony 7.4 also retains its PHP 8.2 baseline, so teams should separately assess whether their PHP runtime and third-party packages remain suitable for their operational and security requirements.

What to do

Keep the application on the latest available 7.4 patch release and use Composer constraints that permit patch-level updates without silently moving to another minor or major line. Run the full test suite, static analysis, and production-like smoke tests after each update. Enable deprecation reporting in development and CI, record deprecations from both application code and third-party bundles, and resolve them continuously rather than postponing them. Review installed bundles, recipes, and PHP extensions for explicit Symfony 7.4 and PHP compatibility before upgrades. In parallel, maintain a tested upgrade branch for the next intended Symfony line, so the eventual move is based on measured compatibility work rather than an emergency dependency upgrade.

Release history

7.x

We can tell you what moving off Symfony 7.4 involves.

What it takes to move off Symfony 7.4 depends on what you built on it — the version you are on, how much depends on it, and how much of the work is mechanical. Leave your email with this version and we can tell you what that looks like for you.

Not sure yet? Get my plan