Updating a site
Minor update of drupal core
composer update drupal/core "drupal/core-*" --with-all-dependencies
drush updb
- Export and commit new config
When not all drupal/core*
modules are updated to the latest stable version, use composer update drupal/core "drupal/core-*" --with-all-dependencies --with=drupal/core-recommended:9.X.0
to see which module causes the error
Find more information in Update core via Composer | Drupal 8 guide on Drupal.org
Major update of drupal core
- Edit composer.json to (all
drupal/core*
packages e.g. from ~8.9.0 => ~ 9.0.0) composer update drupal/core "drupal/core-*" --with-all-dependencies
drush updb
- Export and commit new config
Update modules
Don't forget to run drush updb
after module updates.
According to pinnings
On each H4C update, you should check if the pinned versions have changed. To do so simply run the same script as on install:
./vendor/bin/composer-pin-apply web/modules/contrib/h4c/bin/h4c-tested-global-pinnings.sh
Remove project from composer root (and leave dependency requirement solely to upstream)
- Remove the pinning from composer root:
composer remove drupal/module
Update non-pinned modules
For modules that are not pinned via H4C pinnings, this is the usual composer/drupal procedure:
composer update drupal/module
Update config of H4C (and other modules)
- Update to new module (+theme) version, e.g.
composer update geeks4change/h4c geeks4change/enzian
drush updb
- Do what's described in DO-ON-UPDATE.md since your current version
- Go to
/admin/config/development/configuration/distro
- Select modules, click import config
- Export and commit new config
(See Known issues
section in H4C Config Management module readme)