#Revert drupal core update#
#Revert drupal core code#

#Revert drupal core update#

So, knowing this, one quick way I can get around this problem is to include symfony/* to update the symfony components at the same time as drupal/core: composer update drupal/core symfony/* -with-dependencies Add any blocking dependencies to composer update This gave me a list of a ton of different Symfony components that seemed to be holding back the upgrade, for example:ĭrupal/core 8.5.0 requires symfony/class-loader (~3.4.0)ĭrupal-composer/drupal-project dev-master does not require symfony/class-loader (but v3.2.14 is installed)ĭrupal/core 8.5.0 requires symfony/console (~3.4.0)ĭrupal-composer/drupal-project dev-master does not require symfony/console (but v3.2.14 is installed)ĭrupal/core 8.5.0 requires symfony/dependency-injection (~3.4.0) For example, on this codebase, I know I want to end up with drupal/core:8.5.0, so I can run: composer prohibits drupal/core:8.5.0 Use composer prohibits to figure out what's blocking an updateĬomposer prohibits allows you to see exactly what is preventing a package from being updated. The most important is the command composer prohibits. So, I was searching around for 'how do I figure out why updating something with Composer doesn't update that thing?', and I got a few good answers. You want to update each thing independently so you can test and make sure things don't break. you don't want to be upgrading core and all contrib modules all in one go.

#Revert drupal core code#

If you have a site that uses a number of contrib modules, and maybe even depends on some of their APIs in custom code or in a custom theme. This works, but it's definitely not ideal. Run composer update (updating everything in the entire project, contrib modules, core, other dependencies, etc.).Looking around the web, it seems this is a very common problem, and a lot of people soon go for the nuclear (or thermonuclear 1) option: It remains stubbornly on the previous minor release. I run composer update drupal/core -with-dependencies (as recommended in 's Composer documentation).

I have the version constraint for drupal/core set to ~8.0 or ~8.4 in my composer.json.For both 8.3.x to 8.4.0, and now 8.4.x to 8.5.0, I've had the following issue: For the past two minor release Drupal core upgrades, I've had major problems trying to get some of my Composer-based Drupal codebases upgraded.