Remove wikimedia/composer-merge-plugin

Created on 13 April 2020, about 4 years ago
Updated 14 September 2023, 9 months ago

Problem/Motivation

The wikimedia/composer-merge-plugin was deprecated in Drupal 8.8.0. It was also removed from the project templates and the tarball downloads, and presently only exists in the root-level drupal/drupal repository, which is only used for core development. It should be completely removed in Drupal 9.

Support for Composer 2.x in the wikimedia/composer-merge-plugin is in progress. Removing this plugin will simplify Composer 2 support in Drupal 9.

Proposed resolution

Remove wikimedia/composer-merge-plugin from Drupal's composer.json / lock files. Contrib modules that use wikimedia/composer-merge-plugin must already instruct users to re-add it to their site in order to use it.

Remaining tasks

None.

User interface changes

None.

API changes

None.

Data model changes

None.

Release notes snippet

The wikimedia/composer-merge-plugin dependency has been removed because it is incompatible with Composer 2. It was deprecated in Drupal 8.8.0, and has not been used in core since that release. Any sites that have a separate requirement for this project should add it as a direct dependency.

πŸ› Bug report
Status

Fixed

Version

8.9 ⚰️

Component
ComposerΒ  β†’

Last updated about 22 hours ago

No maintainer
Created by

πŸ‡ΊπŸ‡ΈUnited States greg.1.anderson

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡©πŸ‡°Denmark ressa Copenhagen

    Should the Change Record status be updated to "Published"? It is now in "Draft".

    Also, I see a lot of Change Records where the parent issue is fixed, but the Change Record is still in "Draft".

  • πŸ‡³πŸ‡ΏNew Zealand quietone New Zealand

    @ressa, yes, but before publishing the change record it needs to be reviewed. One can't expect that it is accurate and up to date.

    In this case, I have updated the CR and published it.

  • πŸ‡©πŸ‡°Denmark ressa Copenhagen

    @quietone: I agree 100%, a change record needs to be reviewed before publishing.

    But since the change was rolled out more than three years ago, it's high time the Change record was published.

    And thanks for going through the big back log of Change records β†’ (~100?) and publishing the forgotten ones.

Production build 0.69.0 2024