Why am I unable to update acquia_cms to the latest version?
Date Published: June 30, 2025
This issue occurs when you explicitly require contributed modules that are already included with Drupal Starter Kits. This causes dependency deadlock and slows the upgrade process.
Workaround:
Review dependencies: Review the dependencies listed in your project’s root composer.json file. Identify any modules that are provided by Drupal Starter Kits.
Remove Drupal Starter Kits dependencies: Remove the direct dependencies associated with Drupal Starter Kits from the root composer.json file. This prevents conflicts during the upgrade process.
Run Composer update: After you remove Drupal Starter Kits dependencies, run the following command:
composer update acquia/acquia_cms -W
The -W parameter ensures that your composer.lock file is updated with the latest compatible versions of the dependencies.
By following these steps, you can circumvent the dependency deadlock and enable a seamless update of Drupal Starter Kits to its latest version.
Here is an example of the composer.json file without direct dependencies:
Why am I unable to update acquia_cms to the latest version? | Acquia Product Documentation
Drupal Starter Kits
Why am I unable to update acquia_cms to the latest version?