Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Added note for ece-tools patch process fix #6004

Merged
merged 9 commits into from
Nov 18, 2019
Merged

Added note for ece-tools patch process fix #6004

Changes from 2 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
4a68c2e
Added note for ece-tools patch process fix
meker12 Nov 15, 2019
fe9bda3
Update guides/v2.2/cloud/release-notes/cloud-tools.md
meker12 Nov 15, 2019
c02fe38
Update guides/v2.2/cloud/release-notes/cloud-tools.md
meker12 Nov 15, 2019
7230d53
Updated note about fixes to patch process
meker12 Nov 15, 2019
3728903
Update guides/v2.2/cloud/release-notes/cloud-tools.md
meker12 Nov 15, 2019
ce3c081
Merge branch 'master' into mae-MAGECLOUD-4661
meker12 Nov 15, 2019
dc227da
Update guides/v2.2/cloud/release-notes/cloud-tools.md
meker12 Nov 15, 2019
891de15
Merge branch 'master' into mae-MAGECLOUD-4661
meker12 Nov 18, 2019
3689e76
Removed redundant phrase
meker12 Nov 18, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions guides/v2.2/cloud/release-notes/cloud-tools.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,8 @@ The `{{ site.data.var.ct }}` 2002.0.22 release changes the structure of the `{{

- {:.new}Updated the `composer.json` file for the `{{ site.data.var.ct }}` package to add a dependency for the `magento/magento-cloud-patches` v1.0.0 package.

- {:.fix}<!--MAGECLOUD-4661-->Fixed an issue that caused the `{{ site.data.var.ct }}` patching process to fail when applying security-only patches for versions 2.3.2 and later releases. This issue was introduced by the new versioning scheme adopted for security-only patches in {{ site.data.var.ee }} v2.3.3. See [Security-only patches]({{ site.baseurl }}/guides/v2.3/release-notes/bk-release-notes.html#security-only-patches).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not fail but skip patches, which were expected to apply, causing no patches to be applied at all. This can be better re-worded, it's just the issue itself.

Also I would change ...security-only patches for versions 2.3.2 and later releases. to ...2.3.2-p2 release and any future security-only releases.

Let's call security-only patches as security-only releases to avoid confusion with actual patches (hotfixes), which we fixed. Also new scheme was adopted starting 2.3.2 with 2.3.2-p2 release.


- {:.fix}**Patches and critical fixes**–Update your Cloud environments with `{{ site.data.var.ct }}` 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.

- {:.fix}<!--MAGECLOUD-4649-->**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 {{ site.data.var.ee }} versions 2.3.1 and 2.3.2.
Expand Down