Symfony 7.4 LTS support dates
Bug fixes until November 2028, security fixes until November 2029. Requires PHP 8.2 or higher. Released November 2025 together with Symfony 8.0, which shares the same code minus the deprecated paths.
| Branch | Type | Bug fixes until | Security fixes until | Minimum PHP |
|---|---|---|---|---|
| 6.4 | LTS | 2026-11 | 2027-11 | 8.1.0 |
| 7.4 | LTS | 2028-11 | 2029-11 | 8.2.0 |
| 8.1 | standard | 2027-01 | 2027-01 | 8.4.0 |
| 8.2 | standard | 2027-07 | 2027-07 | 8.4.0 |
7.4 or 8.x?
Symfony 7.4 and 8.0 were released on the same day with the same features. 8.0 only removes what 7.4 deprecates. That is the LTS pattern: get to 7.4, bring deprecations to zero, and 8.x becomes a version bump you can do whenever a bundle asks for it. Standard releases like 8.1 receive fixes for eight months only, so for an application you do not touch every month, 7.4 is the target.
What 7.4 gives you that 6.4 does not
- Three more years of bug fixes than 6.4, whose bug fixes end in November 2026.
- Compatibility with current majors of the ecosystem: API Platform 4.x, Doctrine ORM 3 and DBAL 4, PHPUnit 12 and 13, EasyAdmin 5.
- PHP 8.4 and 8.5 without deprecation noise from the framework itself.
Getting there
From 6.4: deprecations to zero, then one composer update. From 5.4: via 6.4, replacing Guard, Swiftmailer and annotations first. Both paths, with prices, are on services and prices. The free scan tells you which one applies to your composer.lock.
Where does your application stand?
Upload your composer.lock and get your upgrade path, the packages that block it, and a readiness score in seconds. Free, no account, no source code.
Dates verified 2026-09-09 against the official release pages. Other deadlines: Symfony 6.4 end of life · Symfony 5.4 end of life · PHP 8.2 end of life · all end-of-life dates. Also available in Deutsch Nederlands