\Drupal\BuildTests\Composer\Template\ComposerProjectTemplatesTest::testTemplateCreateProject breaks with composer 2.8.1

Caused by https://github.com/composer/composer/pull/12109 (reported there)

Looks like it's 2.8.1 specific issue so we can stick to 2.8.0 https://github.com/composer/composer/issues/12150

I think another test is also affected:

---- Drupal\Tests\Composer\Plugin\Scaffold\Functional\ComposerHookTest ----
Status    Group      Filename          Line Function                            
--------------------------------------------------------------------------------
Exception Other      phpunit-1.xml        0 Drupal\Tests\Composer\Plugin\Scaffo
    PHPUnit Test failed to complete; Error: PHPUnit 10.5.35 by Sebastian
    Bergmann and contributors.
    
    Runtime:       PHP 8.3.12
    Configuration: /builds/security/drupal-security/core/phpunit.xml.dist
    
    E..                                                                 3 / 3
    (100%)
    
    Time: 00:03.088, Memory: 8.00 MB
    
    There was 1 error:
    
    1)
    Drupal\Tests\Composer\Plugin\Scaffold\Functional\ComposerHookTest::testComposerHooks
    RuntimeException: Exit code: 1
    
    Creating a "fixtures/drupal-drupal" project at "./create-project-test"
    Installing fixtures/drupal-drupal (1.0.0)
    
    In PathDownloader.php line 51:
                                                                               
       
      Source path "./drupal-drupal" is not found for package
    fixtures/drupal-drupal                                                                       

AFAICS doing composer self-update 2.8.0 looks like it should be a good workaround until this is resolved upstream.

...that is assuming composer does revert the change. If not, we may have to make more significant changes.

I fixed default version in image to 2.8.0 to prevent re-queue of jobs according to https://git.drupalcode.org/issue/drupal-3479446/-/pipelines

the upstream comment

has 2 guesses abaout caouse commits for phar executable can be patched and tested

andypost → closed merge request !9790

andypost → closed merge request !9789

andypost → closed merge request !9788

I think core need to add to composer conflict { "composer/composer": "<2.8.2" } when it will be released

CR created and MR-update for 10.4 filed too, looking to get it commited

Probably better title is just - Upgrade composer to 2.8.2?

11.x branch appears to need a rebase.

rebased and fixed hash, could get another rebase after 📌 Upgrade open-telemetry packages for PHP 8.4 Active

Rebase seems good, lets see what lands first!

Hey folks, there's three MRs here
One of them looks blank - can we confirm there's one for 11.x and one for 10.4

I think this is eligible to backport to 11.0, 10.3 and 10.2 so if we could also get MRs for that it'd be great

andypost → changed the visibility of the branch 3479446-composer-2-8 to hidden.

removed blank one as it was for testing purposes, curious which version of composer should be used to bump 10.2/10.3?

The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.