Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Install
Works with Drupal: 8.xUsing Composer to manage Drupal site dependencies
Alternative installation files
Download composer_manager-8.x-1.0-beta4.tar.gztar.gz
19.91 KB
MD5: 1ef9174d052e306291e9d0bab5075b96
SHA-1: 4cb4f9d1a0c819c496119cb88cc34d058335940c
SHA-256: 237cc8aeb62ef208f953699b86b015459716c82ee396cafc833944a88c0f2df7
Download composer_manager-8.x-1.0-beta4.zipzip
29.95 KB
MD5: 785d90a1aef683209565ce3ca6b9ab2f
SHA-1: 3eb3745ac3d7cd2f67b3bc0de8ee444679d095e5
SHA-256: 48da4ed34a0661eb0c44d514bb1106a7e6f18e57a7b1bac0ec820e4541ca56a8
Release notes
Breaking changes:
- 'drush composer-manager-init' has been removed. Use 'php modules/composer/manager/scripts/init.php' (renamed from init.sh)
- core/ is no longer modified. Replace your core folder with the one from the tarball or git, to undo the changes the old composer_manager made to composer.json and vendor. Then follow the new instructions from the README.
Changes since 8.x-1.0-beta3:
- Ensure the correct autoload.php even when composer drupal-update is run instead of composer drupal-update during module init.
- Clean up PackageController.
- #2563385 by fsilva, bojanz: Remove SafeMarkup calls in PackageController
- Clean up JsonFile.
- Document the reasoning behind the config property keys.
- #2555453 by mkalkbrenner: Avoid hash updates in composer.lock
- Detect if a composer install is needed, providing better UX for people not following the README.
- Update PackageManagerTest.
- #2452781 followup: Update PackageManager to read the installed packages from the right vendor dir, special case 'composer/installers'.
- #2452781: Modify /composer.json instead of core/composer.json
- Unit tests should run the parent setUp() method.
- Switch to short array syntax.
- #2551145 by chapabu: Tests are failing with latest dev release
- #2553327: Revamp module initialization