Composer, being the dependency manager of Adobe Commerce, is where you will set the version of Adobe Commerce you are targeting. Start by opening and modifying your Composer.json file. are hidden directories (If you're looking at this using windows explorer you'll need to enable hidden items)
Remember that cloud instances can only be modified by pulling down, making changes on a local copy, and then push back to the git branch, which forces a redeploy of the environment.Īfter pulling down your environment, there are 3 key files you have to change in order to downgrade Adobe Commerce.
There is currently no other way to get a downgraded Commerce Cloud project.Īfter Branching from the master project, you can then pull down (clone) the project to your local instance to make changes.
#Magento 2 cloud devdocs install
If you want to install a lower version, you must branch from the main, and then downgrade the branch. The first version of Adobe Commerce cloud you get when obtaining a sandbox will be set-up on the latest Adobe Commerce build. This guide will help you manage your sandbox with multiple instances of Adobe Commerce cloud with varying versions, allowing you to troubleshoot potential issues as you maintain your Commerce extension.
Unfortunately, not every Adobe Commerce customer will be running the most current version of Adobe Commerce – so as an extension developer you may need to maintain your extension so that it supports several recent versions.
0 kommentar(er)
