Download Magento 2 Versions

## Changelog ([4 related PRs](https://github.com/magento/ece-tools/issues?q=label%3A%22Release%3A+2002.0.22%22)) The ece-tools 2002.0.22 release changes the structure of the ece-tools package to decouple the release of Magento Commerce Cloud patches from the ece-tools release. Starting with this release, patches and critical fixes will be delivered using the magento/magento-cloud-patches package, which is a new dependency for the ece-tools package. We made these changes to reduce complexity for scheduling release updates and working with community contributions. **Changes to the ece-tools package** - Moved the Magento Commerce patches from the ece-tools package to a new magento/magento-cloud-patches composer package. - Updated the `composer.json` file for the ece-tools package to add a dependency for the magento/magento-cloud-patches v1.0.0 package. - Fixed an issue that caused the ece-tools patching process to break when applying patch sets on top of security-only releases, starting with Magento version 2.3.2-p2 and later. This issue was introduced by the new versioning scheme adopted for security-only patches. **Patches and critical fixes** - Update your Cloud environments with ece-tools version 2002.0.22 to apply the following patches and critical fixes. These patches are included in the magento/magento-cloud-patches v1.0.0 package. - **Page Builder security patches for 2.3.1.x and 2.3.2.x releases**–Fixes an issue in Page Builder preview that allows unauthenticated users to access some templating methods that can be used to trigger arbitrary code execution over the network (RCE) resulting in global information leaks. This issue can occur when using unsupported versions of Page Builder with Magento Commerce versions 2.3.1 and 2.3.2. - **MSI patches**–Fixes issues that caused indexing errors and performance issues when using default inventory settings for managing stock. - **Backward Compatibility of new Mail Interfaces**-Fixes a backward incompatibility issue caused by the `Magento\Framework\Mail\EmailMessageInterface` PHP interface introduced in Magento Commerce v2.3.3. In the scope of this patch, the new EmailMessageInterface inherits from the old MessageInterface, and Magento Commerce core modules are reverted to depend on MessageInterface. - **Catalog pagination does not work on Elasticsearch 6.x**–Fixes a critical issue with search result pagination that affects customers using Elasticsearch 6.x as the catalog search engine.
Published at 2019-11-14 16:36:54

Download Magento 2002.0.22

## Changelog ([21 related PRs](https://github.com/magento/ece-tools/pulls?utf8=%E2%9C%93&q=label%3A%22Release%3A+2002.0.21%22+)) - **Docker updates**— - **New Docker Images**—Supported by Magento versions 2.3.3 and later - PHP version 7.3. - Varnish Cache 6.2.0 - Added support to apply custom hook configuration specified in `.magento.app.yaml` in the Docker environment. Previously, the Docker environment supported only the default hook configuration. - Docker ENV files are no longer generated during the Docker build, and the `docker:config:convert` command is deprecated. The corresponding data is now stored in the `docker-compose.yml` file. - **Updated PHP image**–Added Node.js to the PHP Docker image to support node, npm, and grunt-cli capabilities. - **Environment variable updates**– - Added the `LOCK_PROVIDER` deploy variable to configure the lock provider which prevents the launch of duplicate cron jobs and cron groups. - Added the `CONSUMERS_WAIT_FOR_MAX_MESSAGES` environment variable to configure how consumers process messages from the message queue when using the `CRON_CONSUMERS_RUNNER` environment variable to manage cron jobs. - Updated the logging information returned by the `module:refresh` command. Now, you can see a detailed list of enabled modules in the `cloud.log` file. - Improved version compatibility validation and warning notifications for compatibility issues between Magento version and installed services, such as Elasticsearch, RabbitMq, Redis, and DB. - Updated interactive validations for service compatibility to reflect supported versions for the new Magento 2.3.3 and 2.2.10 releases. - Improved the log message returned when the cron job management process in the deploy phase tries to stop a cron job that has already finished to clarify that this issue is not an error. Changed the log level from `INFO` to `DEBUG`. - Fixed an issue when running the `setup:upgrade` command that did not interrupt the deployment process when a failure occurred during the `app:config:import` task. - Fixed an issue affecting `WARM_UP_PAGES` functionality that uses a default store URL. Now, if the `config:show:default-url` command cannot fetch a base URL, then the URL from the `MAGENTO_CLOUD_ROUTES` variable is used. - Changed the default log level for the file handler to `debug` to reduce the amount of detail in the log displayed in the Project Web Interface, while still providing detailed information for debugging. - Fixed an issue that can cause database deadlock errors when the `consumers_runner` cron job starts multiple instances of the same consumer on different nodes. Now, if you have enabled the `CRON_CONSUMERS_RUNNER` deploy variable in your environment, the `consumers_runner` job uses the `single-thread` option to start one instance of each consumer on only one node. - Fixed an issue that caused an error with static content deployment during build. After a Magento installation and config dump, an error occurred if there was no locale specified for the admin user in the `config.php` file. Now, there is a default locale for the admin user in the `config.php` file. - Fixed an `Undefined index error` that occurs when a Magento Cloud CLI command fails in an environment that is not configured with a secure URL (https). Now, the ece-tools package uses the base URL (http) if the secure URL is not available.
Published at 2019-09-04 15:39:27

Download Magento 2002.0.21

## Changelog ([30 related PRs](https://github.com/magento/ece-tools/issues?q=label%3A%22Release%3A+2002.0.20%22)) - **Docker Updates**— - You can now perform functional testing using the ECE-Tools package in the Docker environment. - Added support for configuring PHP modules using the `.magento.app.yaml` file. Any PHP Extensions specified in the `.magento.app.yaml` file become available in the Docker PHP containers. - There are new commands available to improve the Docker command line experience. - Added the ability to use Mutagen.io to synchronize files during development between the local host and Docker. - Corrected the default path when using the Docker environment. Now, when you use SSH to log in to the Docker container, you are at the Magento root in the `/app` directory, as expected. - Updated the Sodium library from version `1.0.11` to version `1.0.18`, and updated the Sodium PHP extension. - Added the `analysis-icu` and the `analysis-phonetic` Elasticsearch plugins to all Docker images. - Improved validations: When using options for the `docker:build` command, you must provide a value when using an option. Also, added validation for the Node version when using the `docker:build run` command. - **Environment variable updates**— - Added support for database table prefixes using the `DATABASE_CONFIGURATION` environment variable. - Added the `FORCE_UPDATE_URLS` deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. - Added the `TTFB_TESTED_PAGES` post-deploy variable to configure _Time to First Byte_ page tests to check Magento Commerce application performance on sites deployed to Cloud infrastructure. - Fixed an issue with multi-threaded SCD, which caused random failures in static content deployment. The workaround involved setting the `SCD_THREADS` variable to `1`. You can now increase the count as needed. - You can configure the `WARM_UP_PAGES` environment variable to cache single pages, multiple domains, and multiple pages. - Added the `pub/static/.htaccess` file to the exclude list. - Fixed an error when all validation messages were showing as **Critical** if at least one critical level validator returned an error. - Fixed an issue that caused a deployment failure if the Magento base URL did not exist in the database. - Added a new `env:config:show` command to the ECE-Tools package that displays environment services, routes, or variables. - Fixed an issue that caused a critical error when attempting to install Magento 2.2.6 or earlier with latest ECE-Tools after shell refactoring. - Fixed an issue that caused Magento 2.1.x and 2.2.x installations to fail with a warning about using a deprecated version of `nesbot/carbon`. - Decreased the `cloud.log` log level for shell output from **info** to **debug**. - Added the `--remove-definers (-d)` option to the `ece-tools db-dump` command to remove definers from the dump file.
Published at 2019-06-27 18:02:11

Download Magento 2002.0.20

## Changelog ([1 related PR](https://github.com/magento/ece-tools/pulls?q=is%3Apr+is%3Aclosed+label%3A%22Release%3A+2002.0.19%22)) - Fixed an issue that overwrites the `env.php` file during a deploy, resulting in a loss of custom configurations. This update ensures that ECE-Tools updates the `env.php` file with every deployment, while preserving custom configurations.
Published at 2019-05-24 13:36:01

Download Magento 2002.0.19

## Changelog ([24 related PRs](https://github.com/magento/ece-tools/pulls?q=is%3Apr+is%3Aclosed+label%3A%22Release%3A+2002.0.18%22)) - **Docker Updates**— - Now, the Docker environment supports the cron configuration defined in the crons property of the `.magento.app.yaml` file. - **New Docker Container**—Added a TLS termination proxy container to facilitate the Varnish SSL termination over HTTPS. - **New Docker Image**—Added a Node.js image to support Gulp and other capabilities, such as Jasmine JS Unit Testing. - **Docker build modes**—Now you can choose to launch the Docker environment in Production mode or Developer mode. Developer mode supports active development with full, writable filesystem permissions. This improves the developer experience by providing an easier way to develop and sync extensions, for example. - Fixed an issue that caused Docker deploy to fail with a `Name or service not known` error if the cache is configured for a service that is not available. Now, you can remove a service from the `.magento/services.yaml` file. The Docker configuration generator updates the service in the `docker/config.php.dist` file automatically. - Added interactive validations for service compatibility. Now, if a requested service is incompatible with the Magento version or other services, the _interactive mode_ prompts the user with a message and a choice to continue. See the Service versions available for Docker. Use the `-n` option to skip the interactivity for CICD purposes. - Fixed an issue with the Docker compose `db-dump` command that erased existing dumps. - Fixed an issue that assigned Redis `session`, `default`, and `page_cache` cache storage to the same database ID. - **Environment variable updates**— - The new `ELASTICSUITE_CONFIGURATION` environment variable retains your customized service settings between deployments. - Added the `SCD_MAX_EXECUTION_TIMEOUT` environment variable so you can increase the time to complete the static content deployment from the `.magento.env.yaml` file. - Added the `MAGENTO_CLOUD_LOCKS_DIR` environment variable to configure the path to the mount point for the lock provider on the cloud infrastructure. The lock provider prevents the launch of duplicate cron jobs and cron groups. This variable is supported on Magento version 2.2.5 and later and automatically configured. - Changed the `SCD_THREAD` environment variable default values to automatically determine the optimal value based on the detected CPU thread count. - Fixed an issue with a patch for DB Isolation Mechanism that caused an error when upgrading to ECE-Tools versions 2002.0.16 and 2002.0.17 - Added a patch that replaces _Google Image Charts_ with _Image-Charts_. See the DevBlog article [Google Image Charts deprecation and update for M1](https://community.magento.com/t5/Magento-DevBlog/Google-Image-Charts-deprecation-and-update-for-M1/ba-p/125006). - Added validation for the `SEARCH_CONFIGURATION` variable. Deploy fails when the 'engine' option is not set and `_merge` is not required. - Fixed an issue that exposed sensitive data after an exception occurs. Now the sensitive information is masked appropriately. - Improved the fault-tolerant settings of the ECE-Tools package. In the case when Magento 2 cannot read data from the Redis `slave` instance, a reading is made from the Redis `master` instance.
Published at 2019-05-06 21:30:03

Download Magento 2002.0.18

## Changelog ([8 related PRs](https://github.com/magento/ece-tools/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aclosed+label%3A%22Release%3A+2002.0.17%22+)) The ECE-Tools version 2002.0.17 includes an important security patch. See [Tech Resources: Magento Open Source Patches](https://magento.com/tech-resources/download#download2288). - **Service updates** —Supported by Magento versions 2.3.1 and later 2.3.x versions or 2.2.8 and later 2.2.x versions. - Added support for Elasticsearch version 6.x. - Added support for Redis version 5.0. - **New Docker images**—Added the following services to the Docker build: - Elasticsearch 6.5 - Redis 5.0 - **New environment variable** —Previously, there was a hard-coded timeout for SCD compression. Now you can configure the SCD compression timeout using the `SCD_COMPRESSION_TIMEOUT` environment variable. - Added the --use-rewrites option to the Magento install command so that it uses web server rewrites for generated links in the storefront and Admin access to improve security and customer experience. - Added timestamps to the `var/log/install_upgrade.log` file so that it shows dates for the Magento installation and upgrade events.
Published at 2019-03-28 14:25:43

Download Magento 2002.0.17

## Changelog ([30 related PRs](https://github.com/magento/ece-tools/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aclosed+label%3A%22Release%3A+2002.0.16%22+)) - **Docker updates**— - Now, the default service configuration generated in the Docker environment is the same as the default configuration in the Cloud template. - You can send mail from your Docker environment using the `sendmail` service - Added the ability to configure Xdebug to debug in the Cloud Docker environment. - Fixed an issue with web service permissions when generating the `docker-compose.yml` file. - **Upgrade improvement**—Added validation to confirm that the `autoload` property in the `composer.json` file contains required configuration changes before upgrading to Magentgo v2.3. - The compression process in deploying static content now includes all assets—naively generated or customized—and occurs during the build phase at the beginning of the `build:transfer` section. Previously, the compression process occurred before applying custom minification and bundling of static assets. - Fixed a database connection error that occurred during deployment immediately after configuring an additional database and service relationship. Also, this fix addresses an issue that occurred during the configuration process of MBI for Starter. For Starter, this upgrade is a "must have" for using MBI. - Fixed a validation issue with the database configuration that caused the deploy process to fail. - Updated the constraint with the appropriate version of the `symfony/yaml` package to use with PHP constants. Constant parsing does not work when using a `symfony/yaml` package version earlier than 3.2. - **Environment configuration check**—Added validation to check the PHP version and warn users if they are not using the latest recommended version. - Fixed an issue with processing malformed JSON variables. Now, if a JSON variable causes a syntax error, a warning appears in the `cloud.log` file and deployment continues using the default variable. - Fixed a connection error that occurred during deployment immediately after disabling the Redis service. - **Logging changes**—Updated the log level from `Info` to `Notice` for the following build and deploy process events: - Begin and end of the process for reconciling installed modules in `composer.json` with shared configuration settings in the `app/etc/config.php` file - Begin and end of the configuration validation process - Begin and end of the `setup:di:compile` process for generating classes - **New environment variables**— - **RESOURCE_CONFIGURATION deploy variable**—Use this variable to map a resource name to a database connection. - **X_FRAME_CONFIGURATION global variable**—Use this variable to change the `X-Frame-Options` header configuration for rendering a Magento page in a ``, `