Composer shows "nothing to update" but there is a new version of the module

by Patrick Kenny   Last Updated September 23, 2017 12:07 PM

I am managing a Drupal 8 site in Composer. Commerce 2.0 was just released; I currently have 2.0-rc2 installed on my site.

This is my composer.json

"drupal/commerce": "^2.0@RC",

"minimum-stability": "dev",
"prefer-stable": true,

To update, I ran composer update drupal/commerce --with-dependencies, which gave me this result:

Gathering patches for root package.
Dependency "drupal/core" is also a root requirement, but is not explicitly whitelisted. Ignoring.
Dependency "drupal/core" is also a root requirement, but is not explicitly whitelisted. Ignoring.
Dependency "drupal/core" is also a root requirement, but is not explicitly whitelisted. Ignoring.
Dependency "drupal/core" is also a root requirement, but is not explicitly whitelisted. Ignoring.
Dependency "drupal/core" is also a root requirement, but is not explicitly whitelisted. Ignoring.
Dependency "drupal/core" is also a root requirement, but is not explicitly whitelisted. Ignoring.
Dependency "drupal/core" is also a root requirement, but is not explicitly whitelisted. Ignoring.
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating optimized autoload files
Warning: Ambiguous class resolution, "Drupal\Component\Utility\Random" was found in both "$baseDir . '/web/core/lib/Drupal/Component/Utility/Random.php" and "/mnt/c/Users/patri/d/edosensei/vendor/drupal/drupal-driver/src/Drupal/Component/Utility/Random.php", the first will be used.
Removing packages services cache file:
/mnt/c/Users/patri/d/edosensei/vendor/drupal/console/extend.console.uninstall.services.yml
Creating packages services cache file:
/mnt/c/Users/patri/d/edosensei/vendor/drupal/console/extend.console.uninstall.services.yml
> DrupalProject\composer\ScriptHandler::createRequiredFiles

So Commerce does not get updated to 2.0 (I already updated all the dependencies to their latest versions.)

I thought it might be a caching issue so I ran composer clearcache and then attempted to update commerce again, but I got the same result (nothing to update).

I thought it might be an issue with the composer module list being out of date, but Commerce 2.0 was released more than 48 hours ago. So what can I do to get composer working in this case?



Related Questions


Updating core from 8.2 to 8.3 via composer

Updated April 18, 2017 14:07 PM