Determine why recent versions of Composer fail to resolve self.version strings for Merge Requests

Created on 13 January 2023, almost 2 years ago

Updated 16 February 2023, almost 2 years ago

Problem/Motivation

Sometime on or around January 9th, after 📌 Update PHP 8 containers with latest security release Fixed , DrupalCI testing for Merge Requests began failing with a Composer Error:

00:00:51.277 > Drupal\Composer\Composer::ensureComposerVersion
00:00:51.277 Installing dependencies from lock file (including require-dev)
00:00:51.277 Verifying lock file contents can be installed on current platform.
00:00:51.277 - Required package "drupal/core" is in the lock file as "10.1.x-dev" but that does not satisfy your constraint "self.version".
00:00:51.277 - Required package "drupal/core-project-message" is in the lock file as "10.1.x-dev" but that does not satisfy your constraint "self.version".
00:00:51.277 - Required package "drupal/core-vendor-hardening" is in the lock file as "10.1.x-dev" but that does not satisfy your constraint "self.version".
00:00:51.277 This usually happens when composer files are incorrectly merged or the composer.json file is manually edited.

Most likely, when we updated the PHP containers for the recent security release, the Composer version updated and Composer's 'Guesser' logic must have changed.

Example failures

https://www.drupal.org/project/drupal/issues/3322743 📌 Fix PHPStan L2 errors "Parameter $foo of method Foo::bar() has invalid type Foo\Baz." and "Method Foo::bar() has invalid return type Foo\Baz. " Fixed
https://dispatcher.drupalci.org/job/drupal_patches/161235/console
https://www.drupal.org/i/3313342 →

Proposed resolution

For now:

Roll back/pin a version to get current MRs working
Open a new issue to investigate 'what changed between Composer 2.4.4 and (whatever current version is) to result in bad self.version guessing
Resolve that, then unpin version again

Alternately - once we are pinned on a known working version, seeing if MR testing directly with GitLabCI in those later environments has that problem or not - if not - another reason to keep moving to GitLabCI

Remaining tasks

: https://git.drupalcode.org/project/drupalci_testbot/-/commit/4275bd2f9af...
Separately run some testing on new versions of Composer
Figure out how to fix the testing incompatibility, if we can from our side
If necessary, open upstream bug with Composer team

🐛 Bug report

Status

Fixed

Component

PHP Containers

Created by

🇺🇸United States hestenet Portland, OR 🇺🇸

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment almost 2 years ago →
🇺🇸United States nicxvan
The composer issue was marked as fixed and the pr was merged, once there is a version newer than 2.5.1 we should be able to test updating composer again.
Status changed to Fixed almost 2 years ago5:56pm 16 February 2023
Comment almost 2 years ago →
🇺🇸United States hestenet Portland, OR 🇺🇸
This was fixed in Composer 2.5.2
https://getcomposer.org/changelog/2.5.2

Unpinning again, but leaving steps commented in case this happens in future:
https://git.drupalcode.org/project/drupalci_testbot/-/commit/2b5e1c765f8...
Comment almost 2 years ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024