Symfony 7.3

Symfony 7.3 is a feature release after 7.2 that keeps the Symfony 7 generation's PHP 8.2 baseline and backward-compatibility approach for supported, non-deprecated APIs. It introduced the ObjectMapper component for mapping data between objects and the JsonPath component for querying JSON documents with JSONPath expressions. As with other Symfony feature releases, it also added component-level improvements and deprecations intended to prepare applications for later releases.

Symfony 7.3 has reached end of life. An application can continue to run on it, but upstream will no longer provide maintenance or security fixes for this line. The practical exposure grows when a Symfony defect, security issue, PHP-runtime compatibility problem, or dependency conflict affects the application: remediation may require maintaining a private patch or upgrading under pressure. Packages, bundles, and deployment environments increasingly test against maintained Symfony lines, so retaining 7.3 also raises the chance that routine dependency or platform work becomes blocked or requires version pinning.

Plan an upgrade to a currently maintained Symfony release, with Symfony 7.4 LTS as the usual next target for applications that can meet its dependency requirements. First update to the newest available 7.3 patch level, review Composer constraints and Symfony recipes, and run the full test suite with deprecations enabled through the Symfony PHPUnit Bridge. Resolve deprecations and incompatible third-party bundles before changing the framework constraint, then test application behavior, cache warmup, console commands, authentication flows, forms, serialization, and production deployment builds on the target line. Keep a rollback-tested deployment plan and update the PHP and dependency support baselines alongside the framework upgrade.