dependencies in composer.json and info.yml clash

Created on 30 June 2025, 3 months ago

Problem/Motivation

I can't install alpha 3 with composer because of a requirements problem:

composer require "drupal/localgov_waste_collection:1.0.0-alpha3" --dry-run

  Problem 1
    - Root composer.json requires drupal/localgov_waste_collection 1.0.0-alpha3 -> satisfiable by drupal/localgov_waste_collection[1.0.0-alpha3].
    - drupal/localgov_core 2.14.2 requires drupal/metatag ^2.0.2 -> found drupal/metatag[dev-2.0.x, dev-2.1.x, 2.0.2, ..., 2.1.x-dev (alias of dev-2.1.x)] but it conflicts with your root composer.json require (^1.16).
    - drupal/localgov_core 2.14.7 requires drupal/field_group ^4.0 -> found drupal/field_group[dev-4.x, 4.0.0-alpha1, 4.0.0, 4.x-dev (alias of dev-4.x)] but the package is fixed to 3.6.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - drupal/localgov_waste_collection 1.0.0-alpha3 requires drupal/localgov_core * -> satisfiable by drupal/localgov_core[2.14.2, 2.14.7].

The problem is that while this module's composer.json has:

 "localgovdrupal/localgov_core": "^2.12",

its info file has:

dependencies:
  - localgov_core:localgov_core

and d.org's packaging system appears to merge anything it thinks is present in the info.yml but missing from the composer.json into the resulting packagist metadata:

Doing

> composer show -a drupal/localgov_waste_collection 1.0.0-alpha3

shows:

requires
drupal/core ^10.0 || ^11.0
drupal/localgov_core *
localgovdrupal/localgov_core ^2.12
spatie/icalendar-generator ^2.9

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

1.0

Component

Code

Created by

🇬🇧United Kingdom joachim

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

Merge Requests

Comments & Activities

Production build 0.71.5 2024