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

Commit 7922c66

Browse files
meker12NadiyaS
andauthored
MCLOUD-6073: Review "Update the metapackage" devdocs which is confusing merchants and support agents (#8236) (#8286)
Clarified instructions for specifying meta-package constraint when upgrading the Magento application deployed to the Cloud platform. Co-authored-by: Margaret Eker <meker@adobe.com> Co-authored-by: Nadiya Syvokonenko <nsyvokonenko@magento.com>
1 parent 4261547 commit 7922c66

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

src/cloud/project/ece-tools-upgrade-project.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,11 @@ Each {{site.data.var.ee}} version requires a different constraint based on the f
2727
>=current_version <next_version
2828
```
2929

30+
- For `current_version`, specify the Magento version to install.
31+
- For `next_version`, specify the next patch version after the value specified in `current_version`.
32+
33+
If you want to install Magento `2.3.5-p2`, set `current_version` to `2.3.5` and the `next_version` to `2.3.6`. The constraint `">=2.3.5 <2.3.6"` installs the latest available package for 2.3.5.
34+
3035
You can always find the latest metapackage constraint in the [`magento-cloud` template](https://github.com/magento/magento-cloud/blob/master/composer.json).
3136

3237
The following example places a constraint for the {{site.data.var.ece}} metapackage to any version greater than or equal to the current version 2.3.4 and lower than next version 2.3.5:

0 commit comments

Comments
 (0)