Since #3361983 was committed to Drupal core, psr/http-message needed to be explicitly required for build tests

omkar.podey → made their first commit to this issue’s fork.

Could we just add this to require-dev instead?

AFAICT that would re-introduce the very problem that 📌 Remove psr/http-message from drupal/core-recommended Fixed fixed? 🤔

I think it could be in require-dev with a wide version range though?

Why not use *?

Note that the failure on 10.0.x is pre-existing — see https://www.drupal.org/pift-ci-job/2672722 → , it's been happening for almost 2 months:

So queued a test against 10.1.x.

I think we should commit the last commit \Drupal\Tests\package_manager\Build\TemplateProjectTestBase::createTestProject with a follow-up to figure what the best solution is.

It passes if we put "composer-runtime-api": "^2.1", into require in composer.json because then will be present in the built project in the build test. But if we put require-dev it will not be present. I have confirmed this locally. We don't want to have to our dev dependency in the built project in the build test because then we don't know if the build test will pass without them.

follow-up 🐛 Build tests fail without explicitly requiring psr/http-message Closed: outdated

It'd have been great if the newly added line actually linked to the follow-up issue. Also: might as well have kept this open? Less overhead.

There's less detail in 🐛 Build tests fail without explicitly requiring psr/http-message Closed: outdated than here … so, in the spirit of having actually useful issue summaries: closed 🐛 Build tests fail without explicitly requiring psr/http-message Closed: outdated in favor of reopening this.

Transplanting tags.