Jordi Boggiano

From @daniela-zc 's message: > - Running "composer create-project drupal/recommended-project ." functions correctly. > - However, "composer install" fails to produce the desired outcome. That is interesting, it allowed me...

Yeah this is ultimately a docker build issue. If they don't provide us with a way to detect it we're left with random hacks which may or may not break....

For github and gitlab actions more specifically we might be able to detect those as they have env vars like GITHUB_ACTIONS present but I'm not sure if the env is...

Closing here as I am not sure what we can do to help..

I think we'd need to set up a global composer dir, you can do this by creating a temp dir in the tests and then setting `Platform::putEnv('COMPOSER_HOME', the new temp...

You can try to run `composer self-update --snapshot` before your install step, hopefully that does it, but I'm not sure if it will depending how the action runner you use...

2.4.4 is out now so hopefully you'll get the extra output if it happens again.. But I think what @stof said might be worth looking at as well.

Data from the log you shared above: ``` File size: 2212352 File SHA1: 94bbbeb5bd543070899328131414fd75e6283faa First 100 bytes (hex): 504b03040a00000000008043a956000000000000000000000000180009007068707374616e2d7068707374616e2d373632633464612f555405000181665a64504b03040a00000008008043a9561623f5c87d0200002f0400001f0009007068707374616e Last 100 bytes (hex): 523537cdaeddc421c80fe85b629f96553d0feb7983ccd0ee9c52656a12e8b1955e1cdd2414cd331944377b5bae9bd8b8c7c9c6988d43918b9c5e4ac54e81e6b66cbeeac0bdb2e1c532a2642b526541e5d4951fa3593a9da572a3e20ff3a945aad77935ea ``` Data I got from downloading...

Interesting, seems to be an issue with require, perhaps partial updates. In any case it looks like I can reproduce it. Thanks for the good repro case.

If you run it with `-vvv` and share the output like we ask in the new issue template, maybe you'd see which auth/config file it is loading from when it...