Symfony 7.2

Symfony 7.2 is an incremental feature release in the Symfony 7 major line. Relative to 7.1, it adds the APIs, component improvements, and deprecations introduced during the 7.2 development cycle while retaining the Symfony 7 requirement for PHP 8.2 or later. It follows Symfony's normal major-version compatibility policy: upgrades between supported 7.x feature releases are intended to preserve compatible use of non-experimental public APIs, while deprecated APIs identify code that will need changing before a later major-version upgrade. Applications using the full symfony/symfony package receive the coordinated 7.2 component set; applications requiring individual Symfony components should review each installed component's changelog and dependency constraints.

Symfony 7.2 has reached end of life. The Symfony maintainers no longer provide fixes for newly discovered security issues or defects in this release line. Remaining on it therefore leaves the application dependent on its existing code and on the availability of compensating controls, rather than on upstream remediation. This can increase exposure in security reviews and incident response, especially where Symfony handles authentication, sessions, request parsing, file uploads, serialization, messaging, or externally reachable endpoints. It also makes dependency maintenance harder: newer versions of application libraries may raise PHP or Symfony constraints, and delaying the move can turn a routine in-major upgrade into a larger compatibility project. Existing deployments do not automatically stop working because the line is end of life, but operating reliability and remediation risk are now owned by the team.

Choose a maintained Symfony target that fits the application's PHP version, dependency constraints, and planned major-version path. Start by inventorying composer.json and composer.lock, including Symfony packages installed directly and transitively, PHP extensions, framework bundles, and application code that uses deprecated Symfony APIs. Upgrade in a branch with Composer using compatible Symfony constraints and --with-all-dependencies, rather than selectively changing only the framework package. Run the Symfony PHPUnit Bridge deprecation helper during the upgrade and resolve deprecations that affect the chosen target. Exercise the application through automated and manual tests, with particular attention to container compilation, routing and controllers, forms and validation, security and authentication flows, sessions, cache, console commands, Messenger workers, serialization, and third-party bundles. Deploy first to a representative non-production environment, verify worker restart and cache-warmup procedures, then use a controlled production rollout with monitoring and a rollback plan.