You can upgrade your Magento application from the command line if you installed the software by:
- Downloading the metapackage using
- Installing the compressed archive.
Do not use this method to upgrade if you cloned the Magento 2 GitHub repository. Instead, see Update Magento for upgrade instructions.
The following instructions show you how to upgrade Magento using Composer. Magento 2.4.2 introduced support for Composer 2. If you are attempting to upgrade from Magento <2.4.1, you must first upgrade to a version of Magento that is compatible with Composer 2 (for example, 2.4.2) using Composer 1 before upgrading to Composer 2 for Magento >2.4.2 upgrades. In addition, you must be running a supported version of PHP.
The procedure for upgrading Magento Open Source and Adobe Commerce has changed. You must install a new version of the
magento/composer-root-update-plugin package. In addition, the commands for upgrading have changed from
composer require magento/<package_name> to
composer require-commerce magento/<package_name>.
Before you begin
Complete the following prerequisites to prepare your environment before starting the upgrade process:
- Determine whether your current catalog search engine is supported-Avoid significant upgrade errors by ensuring your search engine complies with 2.4 requirements. See Verify Elasticsearch is installed for more details.
- Complete the Update and upgrade checklist—To avoid possible errors during installation or upgrading, complete the Update and upgrade checklist.
- Set the
pub/directory root—See Modify docroot to improve security for more details.
- Check PHP and environment settings—Verify that your PHP and other environment settings are compatible with the system requirements.
Switch to maintenance mode—To prevent access to your store while it’s being upgraded, switch your store to maintenance mode:
See Enable or disable maintenance mode for additional options.
Optionally, you can create a custom maintenance mode page.
- Check the status of cron jobs—To prevent various unexpected problems during the upgrade, wait for all active running Magento cron jobs to finish or stop them.
Install the Composer update plugin—The
magento/composer-root-update-pluginComposer plugin resolves changes that need to be made to the root project
composer.jsonfile before updating to a new Magento product requirement.
The plugin partially automates the manual upgrade by identifying and helping you resolve dependency conflicts instead of requiring you to identify and fix them manually.
To install the plugin:
composer require magento/composer-root-update-plugin ~2.0 --no-update
Update the dependencies:
See the examples at the end of this section for help specifying different release levels. For example, minor release, quality patch, and security patch. Adobe Commerce customers can access patches two weeks before the General Availability (GA) date. Pre-release packages are available through Composer only. You cannot find them on the Magento Portal or GitHub until GA. If you cannot find these packages in Composer, contact Adobe Commerce Support.
cp composer.json composer.json.bak
Add or remove specific packages based on your needs. For example, if you are upgrading from Magento Open Source to Adobe Commerce, remove the Magento Open Source package.
composer remove magento/product-community-edition --no-update
composer require-commercecommand to upgrade your instance. The command has the following syntax:
composer require-commerce magento/<product> <version> --no-update [--interactive-root-conflicts] [--force-root-updates] [--help]
<product>- (Required) The package to upgrade. For on-premises installations, this value must be either
<version>- (Required) The version of Magento Open Source or Magento Open Source you are upgrading to. For example,
--no-update- (Required) Disables the automatic update of the dependencies.
--interactive-root-conflicts- (Optional) Allows you to interactively view and update any out-of-date values from previous versions, or any customized values that do not match the version you are upgrading to.
--force-root-updates- (Optional) Overrides all conflicting custom values with the expected Magento values.
--help- (Optional) Provides usage details about the plugin.
--force-root-updatesare specified, the command keeps the existing values that are in conflict and displays a warning message.
To learn more about the plugin, refer to the Plugin Usage README.
Magento Open Source:
composer require-commerce magento/product-community-edition 2.4.3 --no-update
composer require-commerce magento/product-enterprise-edition 2.4.3 --no-update
To see the full list of available 2.4 versions:
Magento Open Source:
composer show magento/product-community-edition 2.4.* --available | grep -m 1 versions
composer show magento/product-enterprise-edition 2.4.* --available | grep -m 1 versions
Update the dependencies.
Example - Minor release
Minor releases contain new features, quality fixes, and security fixes. Use Composer to specify a minor release. For example, to specify the Adobe Commerce 2.4.3 metapackage:
1 composer require-commerce magento/product-community-edition 2.4.3 --no-update
Example - Quality patch
Quality patches primarily contain functional and security fixes. However, they can also sometimes contain new, backward-compatible features. Use Composer to download a quality patch. For example, to specify the Adobe Commerce 2.4.1 metapackage:
1 composer require-commerce magento/product-community-edition 2.4.1 --no-update
Example - Security patch
Security patches contain security fixes only. They are designed to make the upgrade process faster and easier.
Security patches use the Composer naming convention
2.4.x-px. Use Composer to specify a patch. For example, to download the Magento Open Source 2.4.3-p1 metapackage:
1 composer require-commerce magento/product-community-edition 2.4.3-p1 --no-update
"description"fields in the
composer.jsonfile as needed.
Updating the metadata in
composer.jsonfile is entirely superficial, not functional.
rm -rf var/cache/*
rm -rf var/page_cache/*
rm -rf generated/code/*
If you use a cache storage other than the filesystem, such as Redis or Memcached, you must manually clear the cache there too.
Update the database schema and data.
Disable maintenance mode.
(Optional) Restart Varnish.
If you use Varnish for page caching, restart it:
service varnish restart
Check your work
Open your storefront URL in a web browser to check whether the upgrade was successful. If your upgrade was unsuccessful, your storefront will not load properly.
If the application fails with a
We're sorry, an error has occurred while generating this email. error:
- Reset file system ownership and permissions as a user with
- Clear the following directories:
- Check your storefront in your web browser again.