Magento 2.4.9 is still in beta, but the scope of changes is already clear – this is not a routine patch release. It is a significant update with deep changes to architecture, dependencies, and platform requirements. Here is what is changing and what you should be thinking about now.
PHP and Platform Requirements
The most important platform-level change: PHP 8.2 is no longer supported. The minimum version is now PHP 8.3, with PHP 8.5 support added.
If you are still running PHP 8.2, upgrading is a hard requirement before moving to 2.4.9. If you are already on 8.3 or 8.4, the path is clear.
Other platform additions: OpenSearch 3.x, Composer 2.9, and Valkey 8.x as a Redis-compatible cache backend alternative with better performance characteristics.
Major Core Replacements
2.4.9 removes several legacy dependencies that have been carried since early Magento 2 versions.
- TinyMCE replaced with HugeRTE – an open-source WYSIWYG editor. This affects custom editor extensions and any code that directly references the TinyMCE API.
- Zend_Cache replaced with Symfony Cache – Adobe reports 30-50% faster cache operations and reduced Redis load. Extensions depending on Zend_Cache classes directly will need to be updated.
- Laminas MVC replaced with a native MVC implementation – another step in Adobe’s ongoing removal of Laminas dependencies across the 2.4.x line.
- Symfony 7.4 LTS – all Symfony dependencies updated. Custom classes that extend Symfony components will need updated method signatures.
- Apache ActiveMQ Artemis – new supported alternative to RabbitMQ for message queues.
What Changes for Developers
Several changes directly affect custom development and integrations:
- GraphQL alias limit – maximum 10 aliases per request. Custom clients sending large batched GraphQL queries should be reviewed.
- GraphQL query length limit – requests above ~1MB will be rejected. Configurable via Admin.
- REST API gallery inheritance fix – updating a product via REST API in a store view scope no longer overwrites images from the global scope. A long-standing issue that broke many custom integrations.
- CAPTCHA for REST and GraphQL – now enforced during account creation via API. Important for headless implementations to account for.
- Native PHP OAuth – the third-party oauth library replaced with native PHP functions. USPS integration migrated to RESTful API with OAuth 2.0.
- New Relic – migrated from deprecated REST API v2 to NerdGraph (GraphQL). Requires Admin configuration update after upgrading.
What Changes for Merchants
- Braintree: Apple Pay now works in Chrome and Firefox, Google Pay vaulting, BLIK for Polish buyers, Pay Upon Invoice for Germany, ELO card type support.
- 2FA: only one enabled provider required instead of all configured ones – simplifies admin access across multiple store views.
- Staging: mobile preview in the browser-simulated device mode.
- Tax rates: bulk delete added to Admin.
Scale of This Release
501 fixes in Magento Open Source, 560 in Adobe Commerce. This is one of the largest releases in the 2.4.x cycle – comparable in scope to 2.4.6.
With this level of core changes, upgrading from 2.4.7 or 2.4.8 will not be straightforward – especially if your project has custom modules with dependencies on Zend_Cache, TinyMCE, Laminas, or Symfony components.
What to Do Now
2.4.9 is still in beta – the final release is expected in Q2 2025. There is time to prepare.
- Check your PHP version. If you are on 8.2, plan the move to 8.3+.
- Audit custom modules for Zend_Cache, TinyMCE, Laminas MVC, and Symfony dependencies.
- Review GraphQL clients for alias count and query sizes.
- If you use New Relic – prepare to update the configuration to NerdGraph after upgrading.
If you want to understand what 2.4.9 means for your specific project, we do upgrade readiness audits. Get in touch.
