Download the Upgrade Compatibility Tool

To get started with the Upgrade Compatibility Tool in a command-line interface, download it by running the following command:

composer create-project magento/upgrade-compatibility-tool uct --repository https://repo.magento.com

The Upgrade Compatibility Tool in a command-line interface

The Upgrade Compatibility Tool is a tool that checks an Adobe Commerce customized instance against a specific version by analyzing all modules installed in it. It returns a list of critical issues, errors, and warnings that must be addressed before upgrading to the latest version of Adobe Commerce.

See this video tutorial (06:02) to learn more about the Upgrade Compatibility Tool.

Available commands for the Upgrade Compatibility Tool in a command-line interface:

Use the upgrade:check command

The upgrade:check command checks for core code changes for that specific Adobe Commerce instance, and all custom code changes installed in it.

The upgrade:check command is the main command to execute the tool:

bin/uct upgrade:check <dir>

Where <dir> value is the directory where your Adobe Commerce instance is located.

Available options for the upgrade:check command:

The Upgrade Compatibility Tool allows you to run the upgrade:check command with an --ignore-current-version-compatibility-issues option. Use this option when you only want to get new issues that are introduced with the update from your current version to the targeted version in your Upgrade Compatibility Tool report:

bin/uct upgrade:check --ignore-current-version-compatibility-issues <dir>

Adding the --coming-version option

You can compare your current Adobe Commerce installation with any Adobe Commerce version >=2.3 by using the --coming-version option.

You must provide the version as a parameter when running the upgrade:check command:

bin/uct upgrade:check <dir> -c 2.4.3

Where -c, --coming-version[=COMING-VERSION] refers to the Adobe Commerce targeted version.

There are some limitations when running the --coming-version:

• This parameter refers to any tag that identifies a specific version of Adobe Commerce.
• It is a requirement to provide this one explicitly; providing only the value of it does not work.
• Provide the tag version without any quotation marks (neither single nor double): ‘2.4.1-develop’.
• You should NOT provide older versions than the one you have currently installed, nor older than 2.3, which is the oldest one supported at the moment.

Use the core:code:changes command

You can compare your current Adobe Commerce installation to validate if the core code of Adobe Commerce was modified to implement a customization. This command shows a list of core modifications only:

bin/uct core:code:changes <dir> <vanilla dir>

Where arguments are as follows:

• <dir>: Adobe Commerce installation directory.
• <vanilla dir>: Adobe Commerce vanilla installation directory.

Available options for the core:code:changes command:

Vanilla installation

A vanilla installation is a clean installation of a specified version tag or branch for a specific release version.

The bin/uct core:code:changes command checks if there is a vanilla instance in your system. If this is the first time using a vanilla installation, an interactive command-line question prompts you to download the vanilla project from the Adobe Commerce repository (https://repo.magento.com/).

You can run an Upgrade Compatibility Tool command with the --vanilla-dir option to specify the Adobe Commerce vanilla installation directory.

See the Deploy vanilla instance topic for more information.

Use the refactor command

The Upgrade Compatibility Tool has the ability to automatically fix a reduced set of issues:

• Functions that were allowed to be used without passing an argument, but with such usage now deprecated.
• Usage of $this in Magento templates.
• Usage of PHP keyword final in private methods.

For that, execute the refactor command:

bin/uct refactor <dir>

Where <dir> value is the directory where your Adobe Commerce instance is located.

Available options for the refactor command:

Use the graphql:compare command

This command provides the option to the Upgrade Compatibility Tool to introspect two GraphQL endpoints and compare their schemas looking for breaking and dangerous changes between them:

bin/uct graphql:compare <schema1> <schema2>

Where arguments are as follows:

• <schema1>: Endpoint URL for the existing installation.
• <schema2>: Endpoint URL for the vanilla installation.

Available options for the graphql:compare command:

Use the list command

To return a list of the Upgrade Compatibility Tool available commands, run:

bin/uct list

Use the --help command

To see the Upgrade Compatibility Tool command general options and help, run:

bin/uct --help

That returns a list with all available help options for the Upgrade Compatibility Tool in a command-line interface:

- -m, --module-path[=MODULE-PATH]: Path of the modules to be analysed
- -a, --current-version[=CURRENT-VERSION]: Current Adobe Commerce version, version of the Adobe Commerce installation will be used if omitted.
- -c, --coming-version[=COMING-VERSION]: Target Adobe Commerce version, latest released version of Adobe Commerce will be used if omitted. Provides a list of all available Adobe Commerce versions.
- --json-output-path[=JSON-OUTPUT-PATH]: Path of the file where the output will be exported in json format.
- --html-output-path[=HTML-OUTPUT-PATH]: Path of the file where the output will be exported in HTML format.
- --context=CONTEXT: Execution context. This option is for integration purposes and does not affect the execution result.
- -h, --help: Display help for that specific command. If no command is provided, `list` command is the default result.
- -q, --quiet: Do not output any messages while executing the command.
- -v, --version: Display application version.
- --ansi, --no-ansi: Enable ANSI output.
- -n, --no-interaction: Do not ask any interactive question while executing the command.
- -v, --vv, --vvv, --verbose: Increase verbosity of output communications. 1 for normal output, 2 for verbose output, and 3 for DEBUG output.

However, it is possible to run --help as an option when running a specific command. This will return specific --help options for that specific command.

Example of the upgrade:check command with --help option:

bin/uct upgrade:check --help

This returns specific options that can be run for the upgrade:check command:

--min-issue-level.
-i, --ignore-current-version-compatibility-issues.

Follow Adobe Commerce Best Practices

• Avoid having two modules with the same name.
• Follow Adobe Commerce coding standards.
• Adobe Commerce 2.4 Upgrade guide best practices.

Optimize your results

The Upgrade Compatibility Tool provides a report containing results with all issues identified on your project by default. You can optimize the results to focus on those issues that you must fix to complete the upgrade:

• Use the option --ignore-current-version-compatibility-issues when you only want to get new issues that are introduced with the update from your current version to the targeted version in your Upgrade Compatibility Tool report.

• Adding the --min-issue-level option, this setting allows to set the minimum issue level, to help prioritize only the most important issues with your upgrade.

• The Upgrade Compatibility Tool requires at least 2GB RAM to run. This setting is recommended to avoid issues due to a low memory limitation. The Upgrade Compatibility Tool displays a question if you run the upgrade:check command with a low memory_limit setting.

• If you want to analyze only a certain vendor, module, or even directory, you can specify the path as an option as well. Run the bin command with the added option -m. This allows the Upgrade Compatibility Tool to analyze a specific module independently, and helps with memory issues that can occur when executing the Upgrade Compatibility Tool. Specify the -m option to run the tool against a specific module:

  bin/uct upgrade:check <dir> -m[=MODULE-PATH]
  

Where arguments are as follows:

• <dir>: Adobe Commerce installation directory.
• [=MODULE-PATH]: Specific module path directory.