:quality(75))
Adobe Commerce 2.4.9 was released on May 12, 2026. It is the annual May feature release under the schedule Adobe moved to in January, and it is a bigger job than the version number suggests — this is the release where a decade of inherited dependencies finally gets removed.
The platform floor moves up
PHP 8.5 and 8.4 are fully supported. PHP 8.3 is allowed for upgrade purposes only and is not recommended for production. PHP 8.2 is no longer supported at all.
On the rest of the stack: MariaDB 11.8 and 12.x are newly supported, 2.4.9 is fully compatible with OpenSearch 3.x, and Valkey 9.x is supported as a Redis alternative.
Read that list as an infrastructure ticket, not a release note. For most merchants the code changes in this release are smaller than the hosting work underneath them.
Three long-standing dependencies removed
This is the part that will decide how long your upgrade takes.
TinyMCE has been replaced with the HugeRTE editor, following TinyMCE's end of support. Laminas MVC has been replaced with a native implementation. Zend_Cache has been replaced by the Symfony Cache component, with the framework now on Symfony 7.4 LTS.
If you have custom modules — and you do — anything that touched the WYSIWYG editor, extended Laminas MVC or called Zend_Cache directly needs looking at before you go anywhere near a production upgrade. That is not a warning about 2.4.9 being unstable. It is a scoping instruction.
The smaller, genuinely useful bits
GraphQL gets clearWishlist and exchangeExternalCustomerToken mutations, which are both the kind of thing headless builds have been working around by hand. The REST API improves product gallery inheritance at store view level — quietly significant for anyone running a lot of store views off one catalogue.
Braintree express checkout expands, including Apple Pay on Chrome and Firefox and a PayPal Contact Module. USPS and DHL shipping integrations have moved to RESTful APIs. There is an admin actions menu for catalogue price rules, which is small and will be appreciated daily by whoever runs your promotions.
One deprecation to note: the "Product was viewed" customer segment condition. If a segment you rely on uses it, check it.
Should you go now
If you are on 2.4.6, the answer is close to yes, because your support runs out on August 11, 2026 and you are choosing between one upgrade and two.
If you are on 2.4.8 and comfortable, there is no emergency — but scope the dependency work now rather than in the week you decide to start. The removals in this release are the sort that turn a two-week upgrade into a six-week one when they are discovered late.