Infrastructure updates—

• Added separate package for Cloud Docker for Commerce—Decoupled the Docker package from the ece-tools package to maintain code quality and provide independent releases. Updates and fixes related to ece-tools are managed from the magento-cloud-docker GitHub repository.

• Updated patching capabilities—Moved the patching functionality from the ECE-Tools package to a separate magento-cloud-patches package. During deployment, ece-tools uses the new package to apply patches. See Cloud patches release notes.

• Updated Composer dependencies—Updated the composer.json file for Adobe Commerce on cloud infrastructure with a dependency for the magento/magento-cloud-docker package. Now, ece-tools includes dependencies for all packages in the Cloud Tools Suite for Commerce. These packages are installed and updated automatically when you install or update ece-tools.

Support for scenario-based deployments—

• Now you can customize the build, deploy, and post-deploy processes using XML configuration files to override or customize the default configuration.

• Changed the hooks configuration in .magento.app.yaml—We updated the hooks configuration format to support scenario-based deployments. The legacy format from earlier ECE-Tools 2002.0.x release is still supported. However, you must update to the new format to use the scenario-based deployment feature. See Scenario-based deployments.

Service updates—

• Added support for PHP 7.3.

• Added support for RabbitMQ 3.8.

• Added validation to check installed service versions against the EOL date for each service. Now, customers receive a notification if a service version is within three months of the EOL date, and a warning if the EOL date is in the past.

• Fixed an Elasticsearch configuration issue to ensure that the correct Elasticsearch settings are configured in all environments.

Environment variable updates—

• Extended the functionality of the WARM_UP_PAGES environment variable to support cache preloading for specific product pages. See the expanded definition in the post-deploy variables topic.

• Added the ERROR_REPORT_DIR_NESTING_LEVEL environment variable to simplify error report data management in the <magento_root>/var/report/ directory. See the variable description in the build variables topic.

• Removed the SCD_EXCLUDE_THEMES, STATIC_CONTENT_THREADS,DO_DEPLOY_STATIC_CONTENT, and STATIC_CONTENT_SYMLINK environment variables. See Backward incompatible changes.

• Fixed an issue in the Elastic Suite configuration process so that the default configuration is overwritten as expected when you configure the ELASTICSUITE_CONFIGURATION deploy variable without the _merge option.

CLI command updates—

• New cron command—You can now manually manage cron processing in your Adobe Commerce on cloud infrastructure environment using the cron:disable and cron:enable commands. Use the disable command to stop all active cron processes and disable all cron jobs. Use the enable command to re-enable cron jobs when you are ready. See Disable cron jobs.

• Improved error reporting—Added better logging for CLI command failures that occur during ECE-Tools processing.

• Remove deprecated build commands— Removed the following build commands: m2-ece-build, m2-ece-deploy, m2-ece-scd-dump, and renamed ece-tools docker commands to ece-docker. See Backward incompatible changes

Removed the deprecated build_options.ini file and added validation to fail the build if the file exists. Use the .magento.env.yaml file to configure build options.

Fixed an issue that caused the build process to fail when the config.php file is empty.