Packages downgraded after upgrading from 2.4.4 to 2.4.4-p1

This article provides a hotfix for the issue when merchants on version 2.4.4 run the composer update command, and then the packages (modules) listed below are getting downgraded to their earlier versions which are not compatible with version 2.4.4 and are only supposed to be used with version 2.4.5 and above.

Affected products and versions

• Adobe Commerce on cloud infrastructure 2.4.4
• Adobe Commerce on-premises 2.4.4
• Magento Open Source 2.4.4

Issue

There are two scenarios how this issue can occur and how it can be reproduced:

Scenario 1

Steps to reproduce:

When upgrading from 2.4.4 to 2.4.4-p1, there is a number of packages (modules) which are downgraded with similar output:

Downgrading magento/module-adobe-ims (2.1.4 => 2.1.3)
Downgrading magento/module-adobe-ims-api (2.1.2 => 2.1.1)
Downgrading magento/module-adobe-stock-admin-ui (1.3.2 => 1.3.1)
Downgrading magento/module-adobe-stock-client-api (2.1.2 => 2.1.1)
Downgrading magento/module-adobe-stock-image (1.3.3 => 1.3.2)
Downgrading magento/module-adobe-stock-image-admin-ui (1.3.3 => 1.3.2)
Downgrading magento/module-banner-page-builder (2.2.3 => 2.2.2)
Downgrading magento/module-inventory (1.2.3 => 1.2.2)
Downgrading magento/module-inventory-admin-ui (1.2.3 => 1.2.2-p1)
Downgrading magento/module-inventory-advanced-checkout (1.2.2 => 1.2.1)
Downgrading magento/module-inventory-api (1.2.3 => 1.2.2-p1)
Downgrading magento/module-inventory-bundle-product (1.2.2 => 1.2.1)
Downgrading magento/module-inventory-catalog-api (1.3.3 => 1.3.2)
Downgrading magento/module-inventory-configurable-product-admin-ui (1.2.3 => 1.2.2-p1)
Downgrading magento/module-inventory-configurable-product-frontend-ui (1.0.3 => 1.0.2)
Downgrading magento/module-inventory-import-export (1.2.3 => 1.2.2)
Downgrading magento/module-inventory-in-store-pickup-admin-ui (1.1.2 => 1.1.1)
Downgrading magento/module-inventory-in-store-pickup-frontend (1.1.3 => 1.1.2)
Downgrading magento/module-inventory-in-store-pickup-graph-ql (1.1.2 => 1.1.1)
Downgrading magento/module-inventory-in-store-pickup-sales-admin-ui (1.1.3 => 1.1.2-p1)
Downgrading magento/module-inventory-in-store-pickup-shipping (1.1.2 => 1.1.1)
Downgrading magento/module-inventory-low-quantity-notification (1.2.2 => 1.2.1)
Downgrading magento/module-inventory-low-quantity-notification-api (1.2.2 => 1.2.1-p1)
Downgrading magento/module-inventory-requisition-list (1.2.3 => 1.2.2)
Downgrading magento/module-inventory-sales-admin-ui (1.2.3 => 1.2.2)
Downgrading magento/module-inventory-sales-api (1.2.2 => 1.2.1)
Downgrading magento/module-inventory-shipping-admin-ui (1.2.3 => 1.2.2-p1)
Downgrading magento/module-inventory-source-selection-api (1.4.2 => 1.4.1-p1)
Downgrading magento/module-inventory-wishlist (1.0.2 => 1.0.1)
Downgrading magento/module-page-builder (2.2.3 => 2.2.2)
Downgrading magento/module-re-captcha-checkout-sales-rule (1.1.1 => 1.1.0)
Downgrading magento/module-re-captcha-customer (1.1.3 => 1.1.2)
Downgrading magento/module-re-captcha-frontend-ui (1.1.3 => 1.1.2)
Downgrading magento/module-staging-page-builder (2.2.3 => 2.2.2)
Downgrading magento/module-two-factor-auth (1.1.4 => 1.1.3)
Removing magento/module-admin-adobe-ims (100.4.0)

Expected results:

The upgrade from version 2.4.4 to 2.4.4-p1 results in the correct packages (modules) for version 2.4.4-p1.

Actual results:

During the upgrade from version 2.4.4 to 2.4.4-p1, these packages' (modules') versions downgrade, but these messages can be ignored, and functionality is not affected.

Scenario 2

Steps to reproduce:

When 2.4.4 merchants run the composer update command, then the same packages (modules) listed above in Scenario 1 get upgraded to their newer versions which are compatible only with version 2.4.5 and are not supposed to be used with version 2.4.4.

Expected results:

The upgrade from version 2.4.4 to 2.4.4-p1 results in the correct packages (modules) for version 2.4.4-p1.

Actual results:

Packages (modules) are downgraded after upgrading from version 2.4.4 to 2.4.4-p1.

Workaround 1: Patch

The patch is attached to this article. To download it, scroll down to the end of the article and click the file name or click the following link: Download ACPLTSRV-2017-fix.sh.zip

Compatible Adobe Commerce and Magento Open Source versions:

The patch was created for:

• Adobe Commerce on cloud infrastructure 2.4.4
• Adobe Commerce on-premises 2.4.4
• Magento Open Source 2.4.4

How to Apply the Patch

Use the attached bash script ACPLTSRV-2017-fix.sh.zip as the workaround for this issue.

Exact instructions how to use the script:

On Adobe Commerce on cloud infrastructure:

1. Download the bash script file ACPLTSRV-2017-fix.sh to your local checkout of your cloud codebase.
2. Run the bash script file ACPLTSRV-2017-fix.sh to modify the composer files locally.
3. Add and commit the modified composer files to your git repository.

On Adobe Commerce or Magento Open Source on-premises:

1. Place the bash script ACPLTSRV-2017-fix.sh in the root folder of your Adobe Commerce/Magento Open Source 2.4.4 installation (the same folder as the composer.json).

2. Run the bash script with an apply argument to lock affected packages (modules) to their 2.4.4 versions:

   sh ACPLTSRV-2017-fix.sh apply
   

3. Run composer updated to install the locked packages (modules).

4. Once you are ready to upgrade to 2.4.5 or 2.4.4-p1, run the script with a rollback argument:

   sh ACPLTSRV-2017-fix.sh rollback
   

   Skipping this step will result in upgrade errors due to conflicting packages (modules) requirements.

5. After completion of the above steps, you can begin upgrading.

Workaround 2

The 2nd workaround for this issue is not to run the composer update command without any arguments.