ÃÛ¶¹ÊÓƵ

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

You may need to give the tool executable permissions with the chmod command:

chmod +x ./uct/bin/uct

The Upgrade Compatibility Tool in a command-line interface

The Upgrade Compatibility Tool is a tool that checks an ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ Commerce installation with any ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ Commerce targeted version.

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

Use the dbschema:diff command

You can retrieve the difference between the database schema of two ÃÛ¶¹ÊÓƵ Commerce versions.

bin/uct dbschema:diff <current-version> <target-version>

Where arguments are as follows:

Example of execution:

bin/uct dbschema:diff 2.4.3 2.4.3-p3

DB schema differences between versions 2.4.3 and 2.4.3-p3:

Table klarna_payments_quote constraint QUOTE_ID_KLARNA_PAYMENTS_QUOTE_QUOTE_ID_QUOTE_ENTITY_ID is present only in version 2.4.3-p3
Table klarna_payments_quote index KLARNA_PAYMENTS_QUOTE_SESSION_ID is present only in version 2.4.3-p3
Table customer_entity column session_cutoff is present only in version 2.4.3-p3
Table customer_visitor column session_id length value is different. 2.4.3: "64", 2.4.3-p3: "1"
Table customer_visitor column session_id comment value is different. 2.4.3: "Session ID", 2.4.3-p3: "Deprecated: Session ID value no longer used"
Table customer_visitor column created_at is present only in version 2.4.3-p3
Table oauth_consumer column secret length value is different. 2.4.3: "32", 2.4.3-p3: "128"
Table oauth_token column secret length value is different. 2.4.3: "32", 2.4.3-p3: "128"
Table admin_user_session column session_id nullable value is different. 2.4.3: "false", 2.4.3-p3: "true"
Table admin_user_session column session_id length value is different. 2.4.3: "128", 2.4.3-p3: "1"
Table admin_user_session column session_id comment value is different. 2.4.3: "Session ID value", 2.4.3-p3: "Deprecated: Session ID value no longer used"

Total detected differences between version 2.4.3 and 2.4.3-p3: 11

Use the core:code:changes command

You can compare your current ÃÛ¶¹ÊÓƵ Commerce installation to validate if the core code of ÃÛ¶¹ÊÓƵ 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:

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 ÃÛ¶¹ÊÓƵ Commerce repository (https://repo.magento.com/).

You can run an Upgrade Compatibility Tool command with the --vanilla-dir option to specify the ÃÛ¶¹ÊÓƵ Commerce vanilla installation directory.

See the topic for more information.

Use the refactor command

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

For that, execute the refactor command:

bin/uct refactor <dir>

Where <dir> value is the directory where your ÃÛ¶¹ÊÓƵ 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:

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:

- --raw             To output raw command list
- --format=FORMAT   The output format (txt, xml, json, or md) [default: "txt"]
- --short           To skip describing commands' arguments
- -h, --help            Display help for the given command. When no command is given display help for the list command
- -q, --quiet           Do not output any message
- -V, --version         Display this application version
- --ansi|--no-ansi  Force (or disable --no-ansi) ANSI output
- -n, --no-interaction  Do not ask any interactive question
- -v|vv|vvv, --verbose  Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug

It is possible to run --help as an option when running a specific command. It returns --help options for the specified 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:

- -a, --current-version[=CURRENT-VERSION]: Current ÃÛ¶¹ÊÓƵ Commerce version, version of the ÃÛ¶¹ÊÓƵ Commerce installation will be used if omitted.
- -c, --coming-version[=COMING-VERSION]: Target ÃÛ¶¹ÊÓƵ Commerce version, latest released version of ÃÛ¶¹ÊÓƵ Commerce will be used if omitted. Provides a list of all available ÃÛ¶¹ÊÓƵ 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.
- --min-issue-level[=MIN-ISSUE-LEVEL]            Minimal issue level you want to see in the report (warning, error or critical). [default: "warning"]
- -i, --ignore-current-version-compatibility-issues  Ignore common issues for current and coming version
- --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.

Follow ÃÛ¶¹ÊÓƵ Commerce 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: