Open BarnyShergold opened 3 years ago
The constraint numbers for the metapackage don't need to be set as : >=current_version <next_version
eg "magento/magento-cloud-metapackage":">=2.3.4 <2.3.5"
"magento/magento-cloud-metapackage":">=2.3.4 <2.3.5"
This is because the Cloud metapackage require does this -
"require": { "fastly/magento2": "^1.2.34", "magento/ece-tools": "^2002.1.0", "magento/module-paypal-on-boarding": "~100.4.0", "magento/product-enterprise-edition": ">=2.4.2 <2.4.3" },
Change "magento/magento-cloud-metapackage":">=2.x.y <2.x.z" to "magento/magento-cloud-metapackage":"2.x.y" in composer.json
"magento/magento-cloud-metapackage":">=2.x.y <2.x.z"
"magento/magento-cloud-metapackage":"2.x.y"
There is an issue on DEVDOCS for the docs - https://github.com/magento/devdocs/issues/9094
Description
The constraint numbers for the metapackage don't need to be set as : >=current_version <next_version
eg
"magento/magento-cloud-metapackage":">=2.3.4 <2.3.5"
This is because the Cloud metapackage require does this -
Possible solutions
Change
"magento/magento-cloud-metapackage":">=2.x.y <2.x.z"
to"magento/magento-cloud-metapackage":"2.x.y"
in composer.jsonThere is an issue on DEVDOCS for the docs - https://github.com/magento/devdocs/issues/9094