You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: src/guides/v2.4/comp-mgr/cli/cli-upgrade.md
+24-7Lines changed: 24 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,9 @@ Do not use this method to upgrade if you cloned the Magento 2 GitHub repository.
20
20
21
21
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]({{page.baseurl}}/install-gde/system-requirements.html) of PHP.
22
22
23
+
{:.bs-callout-warning}
24
+
The procedure for upgrading {{site.data.var.ce}} and {{site.data.var.ee}} has changed. You must install a new version of the Composer update plugin. In addition, the commands for upgrading have changed from `composer require magento/<package_name>` to `composer require-commerce magento/<package_name>`.
25
+
23
26
## Before you begin {#prerequisites}
24
27
25
28
Complete the following prerequisites to prepare your environment before starting the upgrade process:
@@ -72,28 +75,42 @@ See the examples at the end of this section for help specifying different releas
1. Indicate the Magento packages, both the edition (`community` or `enterprise`) and the version (`{{ page.guide_version }}.0`), that you want to upgrade to.
78
+
1. Run the `composer require-commerce`command to upgrade your instance. The command has the following syntax:
76
79
77
-
{:.bs-callout-info}
78
-
The first time you upgrade using the plugin, you can interactively view and update any out-of-date values that may be remaining from previous versions.
79
-
To enable this, use the `--interactive-root-conflicts` option on the `composer require-commerce` commands.
`<product>` - (Required) The package to upgrade. For on-premise installations, this value must either `product-community-edition` or `product-enterprise-edition`.
80
87
81
-
To override all conflicting custom values with the expected Magento values, re-run the `composer require-commerce`command with the `--use-default-project-values` option.
88
+
`<version>` - (Required) The version of {{site.data.var.ce}} or {{site.data.var.ce}} you are upgrading to. For example, `2.4.4`.
89
+
90
+
`--interactive-root-conflicts` - (Optional) Allows you to interactively view and update any out-of-date values that may be remaining from previous versions.
91
+
92
+
`--force-root-updates` - (Optional) Overrides all conflicting custom values with the expected Magento values.
93
+
94
+
`--no-update` - (Optional) Disables the automatic update of the dependencies.
95
+
96
+
If neither `--interactive-root-conflicts` nor `--force-root-updates` are specified, the command keeps the existing values that are in conflict and displays a warning message.
82
97
83
98
{:.bs-callout-tip}
84
99
Use `composer require-commerce --help` to learn more about available options.
85
100
To learn more about usage of the plugin, refer to the [Plugin Usage](https://github.com/magento/composer-root-update-plugin/blob/0.1/src/Magento/ComposerRootUpdatePlugin/README.md#usage).
0 commit comments