ÃÛ¶¹ÊÓƵ

To streamline the ÃÛ¶¹ÊÓƵ Commerce lifecycle policy and support the mission-critical needs of customers, ÃÛ¶¹ÊÓƵ expanded the support window to three years from the General Availability (GA) date for ÃÛ¶¹ÊÓƵ Commerce 2.4.4 and later. ÃÛ¶¹ÊÓƵ provides quality fixes to the 2.4.4 and later releases for a three-year support period. Customers can access quality fixes by contacting ÃÛ¶¹ÊÓƵ Commerce Support or through the self-serve Quality Patches Tool if their version is still eligible for quality support. The following table described end of software support dates for the ÃÛ¶¹ÊÓƵ Commerce release lines.

ÃÛ¶¹ÊÓƵ provides security fixes through a security patch release for the three-year support period.

For critical security issues, such as zero-day vulnerabilities, ÃÛ¶¹ÊÓƵ provides for all customers on a supported version, even if they are not on the latest patch or security patch release. Note that a hotfix is not comprehensive and does not address all security issues that would be resolved by upgrading to the latest release.

ÃÛ¶¹ÊÓƵ does not provide security and quality fixes for third-party services and software dependencies (such as PHP and MySQL) that may reach end of life while customers are on the three-year support period for ÃÛ¶¹ÊÓƵ Commerce. See the system requirements for a full list of tested and supported third-party technologies.

For ÃÛ¶¹ÊÓƵ Commerce on Cloud customers using versions 2.4.4 and 2.4.5, ÃÛ¶¹ÊÓƵ automatically applies PHP 8.1 lifetime security fixes to the infrastructure, so these customers are not impacted by PHP 8.1 end-of-support. On-premises customers using ÃÛ¶¹ÊÓƵ Commerce 2.4.4 and 2.4.5 must contact ÃÛ¶¹ÊÓƵ Support to request PHP 8.1 lifetime security patches if needed.

ÃÛ¶¹ÊÓƵ provides compatibility with third-party services and software dependencies while customers are on the three-year support period for ÃÛ¶¹ÊÓƵ Commerce in the scope of security-only patch releases, but only when it is possible to do so without introducing backward-incompatible changes.