Upgrading Adobe Commerce
If you are upgrading Adobe Commerce on cloud infrastructure, try the following to resolve conflicting component dependencies:
- Check the keys being used to upgrade. Are the keys being generated from the correct email account?
- Check permissions and make sure that they match the Magento upgrade requirements. Review Magento Upgrade Overview > Update and Upgrade Checklist > File System Permissions in our developer documentation.
Incompatibility with third-party modules:
Conflicting component dependencies can also be caused by third-party modules that depend on earlier Commerce components than the ones you have installed. Try the following:
- In the preceding example, the installed package magento/sample-data version 0.74.0-beta15 cannot be upgraded to 1.0.0-beta. However, 0.74.0-beta15 can be upgraded to 0.74.0-beta16 (or others). Edit
composer.json
to make any of these changes. Typically, the versions your project is requesting will be defined in therequire
orrequire-dev
property of the object in that JSON file. Depending on the options of package versions provided, they might specify a specific version or a constraint. For general guidance on how to use composer, if you are on our cloud infrastructure, you can refer to Cloud for Adobe Commerce > Technologies and Requirements > Composer in our developer documentation. If you are on Adobe Commerce on-premises, refer to Adobe Commerce > Installation Guide > Install Adobe Commerce Using the Composer . - Now try the readiness check. Review Adobe Commerce Upgrade Overview > Run the Module Manager > Step 1 Readiness Check in our developer documentation.
- If the readiness check fails with another Component dependency check failure message, click on the following links depending on whether you are using Adobe Commerce or Magento Open Source to get further troubleshooting steps.