IMO, this is always a bad idea unless you feel safe upgrading all the things all the time (for some simple sites, this might not be the worst idea, but it still removes all the dependency management control you get when using Composer properly).
#PANTHEON UPDATE DRUPAL CORE UPDATE#
Finally, I updated the documentation page Update core via Composer (option 4) and added a little bit of the information above in the troubleshooting section, because I'm certain I'm not the only one hitting these issues time and again, every time I try to upgrade Drupal core using Composer!ġ The thermonuclear option with Composer is to delete your vendor directory, delete your lock file, hand edit your composer.json with newer package versions, then basically start over from scratch. I learned a bit following the discussion in the issue composer fail to upgrade from 8.4.4 to 8.5.0-alpha1, and I also contributed a new answer to the Drupal Answers question Updating packages with composer and knowing what to update. You'd think all of the ones listed by composer prohibits are blocking the upgrade, but as it turns out, only the symfony/config dependency (which is a dependency of Drush and/or Drupal Console, but not Drupal core) was blocking the upgrade on this particular site! Unfortunately, it's more difficult to figure out which dependencies exactly are blocking the 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.
#PANTHEON UPDATE 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.
0 kommentar(er)
