Magento-cloud-metapackage

0 views
Skip to first unread message

Colby DuLin

unread,
Aug 5, 2024, 2:33:22 AM8/5/24
to boiturtile
Firstoff, any answers that suggest removing or editing the composer.lock file directly are wrong. Deleting composer.lock and regenerating will effectively upgrade every package to the latest version as specified by your composer.json file, and you should never edit the lock file directly.

magento/magento-cloud-metapackage is, as its name suggests, a meta-package - AKA a package that represents a collection of other packages that go together, as opposed to a module of code. In this case, the main dependency (or sub/child-package) here is magento/product-enterprise-edition which has been locked to an older version per your composer.lock.


Assuming you don't have both the cloud and enterprise packages in your composer.json, what you need to tell Composer is that you want to upgrade magento/magento-cloud-metapackage and any of its sub-packages or dependencies. Conveniently enough, composer update has a flag you can use for this.


I suspect it's just that it goes to search the wrong version name. What if you edit directly your composer.json magento/magento-cloud-metapackage : 2.4.5-p2 and replace it by magento/magento-cloud-metapackage : 2.4.6


Problem 1 - The requested package magento / magento-cloud-metapackage could not be found in any version, there may be a typo in the package name. Potential causes: - A type in the package name - The package is not available in a stable-enough version according to your minimum-stability setting see for more details. - It's a private package and you forgot to add a custom repository to find it


***[InvalidArgumentException] Package magento / magento-cloud-metapackage not found I also thought that it is a credential issue but my credentials correspond to the public and private key that magento markeplace informs. Please help.


We had the same problem. In our case the problem was solved by using the same keys as the Magento cloud project account owner. Merely using other individuals' marketplace keys - even though they are members/superusers of said Magento cloud project - apparently won't do.


ERROR:



Problem 1 - magento/magento-cloud-metapackage 2.3.1 requires magento/product-enterprise-edition 2.3.1 -> satisfiable by magento/product-enterprise-edition[2.3.1] but these conflict with your requirements or minimum-stability. - magento/magento-cloud-metapackage 2.3.1-p1 requires magento/product-enterprise-edition 2.3.1 -> satisfiable by magento/product-enterprise-edition[2.3.1] but these conflict with your requirements or minimum-stability. - magento/magento-cloud-metapackage 2.3.1-p1 requires magento/product-enterprise-edition 2.3.1 -> satisfiable by magento/product-enterprise-edition[2.3.1] but these conflict with your requirements or minimum-stability. - Installation request for magento/magento-cloud-metapackage >=2.3.1 satisfiable by magento/magento-cloud-metapackage[2.3.1-p1, 2.3.1].


Please make sure the version in the compser.json file. It should be updated version 2.3.5. If not then update version 2.3.5 and I am assuming it is cloud magento version then update magento-cloud-metapackage version on composer.json file as per mentioned below:

3a8082e126
Reply all
Reply to author
Forward
0 new messages