Released on March 14, 2023, Adobe Commerce 2.4.6 cropped up with improved scalability and performance trait. Besides, Magento/Adobe Commerce Cloud is in place to roll out its next feature-packed version, 2.4.6-p1, on June 13, 2023.

This post will unveil the top improvements and updates of these all-new release notes to assist you in making the most out of Adobe versions 2.4.6 and 2.4.6-p1.

Let’s get started!

Adobe Commerce

Adobe Commerce Version 2.4.6 – Top Highlights

Adobe Commerce version 2.4.6 emerged with support for PHP 8.2; also, its third-party libraries and Core Composer dependencies have been upgraded to the latest versions compatible with PHP 8.2. The support for PHP 7.4 has already been removed, but for PHP 8.1, it stays the same, fully supported. Besides, the release includes about 300+ quality fixes and enhancements. 

Platform Enhancements

As we have discussed, Adobe Commerce 2.4.6 already supports PHP 8.1, introduced support for PHP 8.2, and removed the support for PHP 7.4 from this release. 

Let’s Review the Supports You Can Get from Adobe Commerce 2.4.6: 

  • Elasticsearch 8.x has been upgraded.
  • Composer 2.2.x. Composer 1.x has been removed.
  • This version supports Redis 6.2, but Adobe recommends that users deploy this latest release with Redis 7.0.x as Redis 6.2 is likely to end up in 2024
  • OpenSearch is already supported as an independent search engine for Magento Open Source, but this version supports it as the default search engine for Magento/Adobe Commerce cloud and on-premises deployment.
  • This release note has been tested with OpenSearch 2.5 and supports OpenSearch v2.x.
  • Compatibility with OpenSearch 1.x still exists, but Adobe recommends its users use this version with OpenSearch 2.x. One can install and run Magento Open Source and Adobe Commerce 2.4.6 with OpenSearch 2.x on on-premises and Cloud Search engine prerequisites. 
  • Adobe recommends upgrading to MariaDB 10.6, although Adobe Commerce 2.4.6 is still compatible with MariaDB 10.4

Note: However, not all the releases introduce major backward-incompatible changes (BICs). But, Magento Open Source and Adobe Commerce releases may include BICs. To review the BICs, visit the BIC reference, and for the major backward-incompatible issues, check the description in BIC highlights

Other Replacements & Upgrades

  • Outdated JavaScript libraries have been upgraded to their newest versions. Also, outdated dependencies have been eliminated. Such changes are backward compatible. 
  • Symfony dependencies have been updated to the latest LTS version. The dependencies this version includes are:
1. web-token/jwt-framework
2. symfony/finder
3. symfony/console
4. symfony/process
5. symfony/event-dispatcher
6. friendsofphp/php-cs-fixer
  • Migration of the DHL schema from v6.2 to v10.0.
  • PHP 7.4 compatibility has been eliminated from the Commerce codebase. 
  • Upgraded jQuery/fileUpload library to v10.32.
  • Laminas dependencies have been upgraded to support PHP 8.2.
  • jquery-migrate has been removed from the Commerce codebase. 
  • Upgraded web-token/jwt-framework to v3.0.5. (latest version)
  • Upgraded the Chart-js library to v3.9.1
  • Upgraded allure-framework/allure-phpunit to v2.x.
  • Replaced Zend_Filter with laminas/laminas-filter.
  • Outdated Zend framework (ZF1) components have been removed from the codebase. 

Security Enhancements

You will find eight security fixes and the platform security improvements in Adobe Commerce 2.4.6.

To date, no confirmed issue-relevant attacks haven’t been cropped up. However, one can potentially exploit certain vulnerabilities for customer information access or to take over administrator sessions. In some of such issues, an attacker should first obtain access to the Admin, resultantly, Adobe team will remind the users to follow all the significant steps to safeguard Admin, like:

  • Good password hygiene
  • Use of a VPN
  • IP allowlisting
  • Prefer using an exceptional location despite /admin. 
  • Two-factor authentication

Additional Security Enhancements

For Adobe Commerce 2.4.6 release note, the security improvements enhance compliance with the recent security best practices, including:

  • During payment processing, when unexpected errors emerge, you will not experience reCAPTCHA validation failure, even during checkout. 
  • In Admin action logs, gaps have been caught with more explicit auditing of actions within mass actions, grid views, and exports. 
  • When an admin user alters their email, a new system configuration is for the needed email confirmation. 

Performance And Scalability Enhancements

  • Enhanced high-throughput order processing performance through load balancing.
  • Improved import performance (up to 100,000 records per minute)
  • New system configuration setting for restricting the number of products showcased in the product grid.
  • Enhanced performance for the operations affecting various customer segments. 

There are more upgrades and enhancements included in Adobe Commerce 2.4.6 release note, like PWA studio and page builder compatibility, Braintree payment features upgrade, GraphQL performance enhancements, accessibility updates, and more that will appear as a big help for your business. 

Next, we will put some light on the upcoming version of Adobe 2.4.6-pt1

Adobe Commerce 2.4.6-p1 Release Notes – Top Highlights

The upcoming security release from Adobe, Adobe Commerce 2.4.6-p1, offers three security fixes that lead to improved Adobe Commerce 2.4.6 or Magento Open Source 2.4.6 deployment. Moreover, it crops up with fixes for the vulnerabilities identified in the previous one. 

This release note includes the security enhancements that improve compliance with the new security best practices. Such improvements include thirteen platform upgrades and fixes. 

Security Patches

Platform Upgrades

This update for the newest release improve compliance with the recent best practices for security. 

  • RabbitMQ 3.11 support
  • JavaScript Libraries
  • Varnish cache 7.3 support

Security Fixes

It arrives with thirteen security fixes. The default behavior of the isEmailAvailable GraphQL query and (V1/customers/isEmailAvailable) REST endpoint has changed. 

Security Highlight

The default behavior of the isEmailAvailable GraphQL query and (V1/customers/isEmailAvailable) REST endpoint has changed. 

  • By default, the API now always returns true.
  • Merchants can enable the original behavior; if the email exists, it will return false, and if it doesn’t, it will return true

Known Issue

The nginx.sample file was inadvertently updated with a change that changes the value of fastcgi_pass from fastcgi_backend to php-fpm:9000. This modification can be ignored or safely reverted. 



Well, if you belong to a technical background, you will grasp these upgrades and enhancements easily. But, if you are not tech-savvy, then let you know that you would need assistance from a Magento 2 Development Company with notable years of experience and a proven track record of offering customized Magento 2 Development services

Connect with an expert today to get your project started right away! 

Ajit Jain

Ajit Jain has been working as a Magento specialist for quite some time now, and he has all the credentials to back up his claim to the title. In addition, he has extensive experience in designing and implementing high-performance, integrated, and complicated eCommerce systems. He has evidently used his talent to great effect at Emizentech in the Adobe e-Commerce development solutions.