Skip to content

Releases: magento/magento-cloud-patches

1.0.10

10 May 19:40
ac81526
Compare
Choose a tag to compare

1.0.6

05 Aug 20:16
10ea637
Compare
Choose a tag to compare

1.0.5

24 Jun 16:56
7da8f36
Compare
Choose a tag to compare

1.0.4

11 May 20:09
54df094
Compare
Choose a tag to compare

1.0.3

04 Mar 14:59
7527aa6
Compare
Choose a tag to compare

1.0.2

26 Feb 14:53
00dc06e
Compare
Choose a tag to compare

1.0.1

05 Feb 21:49
088d258
Compare
Choose a tag to compare

Changelog (7 related PRs)

We have included all Magento Open Source 2.x patches from the Magento Technical resources in the magento-cloud-patches v1.0.1 release. If you copied any patches into your project previously, remove them to avoid conflicts.

This release includes the following updates:

  • Fix cron deadlocks and improve cron locking–
    • Fixes an issue with some cron jobs not running due to an incorrect status value in the cron_schedule table. Now, we use the Magento lock framework to check and update cron job status instead of using the cron_schedule table. Cron jobs that have ended with an error status are retried during the next cron run instead of waiting 24 hours.
    • Adds a retry operation to avoid deadlock during updates to the data in the cron_schedule table.
  • Updated patches to include all available patches for Magento Open Source 2.x–Updated the magento-cloud-patches package to include all Magento Open Source 2.x patches available on the Magento Download page. If you copied any Magento Open Source patches into your Magento Commerce Cloud project previously, remove them to avoid conflicts.
  • Updated patch for Elasticsearch catalog pagination fix –Replaced the Elasticsearch catalog pagination patch delivered in magento-cloud-patches v1.0 with a more effective fix.
  • Updated the Magento Page Builder patches–In Magento Cloud Patches 1.0.0, we bundled Page Builder patches to address a known Page Builder remote code execution (RCE) vulnerability, with the initial fix based on Magento 2.3.3. We have updated these patches with a more stable implementation based on Magento 2.3.4, which includes multiple optimizations for fixing the issue. If you have the magento-cloud-patches 1.0.0 package, you are still protected from the Page Builder RCE vulnerability issues. If you update to magento-cloud-patches 1.0.1 or later, you have a better implementation of the same fix.

1.0.0

14 Nov 16:37
Compare
Choose a tag to compare

Changelog (6 related PRs)

Overview—

  • The ece-tools 2002.0.22 release changes the structure of the ece-tools package to decouple the release of Magento patches from the main ece-tools release. Starting with this release, patches and critical fixes will be delivered using this repository and respective 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.

Patches and critical fixes—

  • Update Cloud environment to use magento-cloud-patches version 1.0.0 to apply the following critical fixes:
    • Page Builder security patches for 2.3.1 and 2.3.2 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). 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 2.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.