Then I manually edited the composer.json file and changed the version constraint for topfloor/composer-cleanup-vcs-dirs to: "topfloor/composer-cleanup-vcs-dirs": "dev-composer-2"Ĭomposer update topfloor/composer-cleanup-vcs-dirs
So, while still using Composer 1, I did the following (on my local, of course):Ĭomposer update cweagans/composer-patches Then, update drupal/core + its dependencies only. topfloor/composer-cleanup-vcs-dirs - the "dev-composer-2" branch is compatible with Composer 2 Problem/Motivation Currently you need to specify alpha, beta or rc, to download the latest Drupal 10 release with Composer: composer create-project -n drupal/recommended-project:10.0.0-alpha It would be great if this syntax was supported, so you automatically got alpha-3, alpha-4, beta-1, rc-1, etc.Drupal 10.0.x will receive security coverage until December 2023. cweagans/composer-patches - compatible with Composer 2 starting with 1.7.0 This is a patch (bugfix) release of Drupal 10 and is ready for use on production sites.composer/installers - compatible with Composer 2 starting with 1.9.0.In this case of the codebase, there were three Composer plugins to review: So, the first step, prior to updating to Composer 2, is to ensure all plugins are ready for Composer 2.
Dependencies are committed to the project Git repository.I've had a few people ask me about the process, so I thought I'd write up what it took to update this site to Composer 2. I figured it would be a pretty easy process, and I was correct.
#DRUPAL COMPOSER UPDATE HOW TO#
After teaching folks how to use Composer effectively over the past couple of years, I figured it was time for me to (finally) update to use Composer 2.
0 kommentar(er)
