Testbench Core v7.9 Gets Installed With Laravel 9.2.0 (and cause Access to undeclared static property $latestResponse error)

[fulopattila122]

Hi There,

I'm kinda puzzled by the issue below, which is - as far as I see - likely a composer issue I never met before.

We have packages that support Laravel 9.2 as the minimum version, and we instrument the CI pipeline to install Laravel 9.2.
Orchestral Testbench and Testbench Core have properly set their Laravel dependencies within the 7.x series,
still, for some reason, Testbench Core 7.9 gets installed along with Laravel 9.2.0:

What I find odd is that composer properly detects the conflict between Laravel 9.2.0 and Testbench 7.2.0:

..but with Testbench Core, it sees no such constraints:

Even though composer is apparently aware of the minimum Laravel requirement, (which is not met):

What I would expect is that composer detects that Orchestra Testbench Core v7.1 is the highest version it should install and act accordingly.

I tried:

• Testing locally and in CI
• Testing with another package
• Upgrading composer to the latest (2.4.2) version
• Adding orchestra/testbench-core as a root requirement (besides orchestra/testbench)

all bringing the same result.

Does anyone have an idea what is causing this?

[crynobone]

Can't debug without looking at the actual composer.json and CI pipeline.

[crynobone]

You issue is that you force Laravel Framework to require 9.2.x but everything else can install highest dependencies. When testing lowest deps you should ensure all dependencies are running on the lowest version and not just the Framework.

[fulopattila122]

Thanks a lot for the quick solution. It solves the problem in the CI; however, I still don't get how composer allows testbench core 7.9 besides Laravel 9.2 when testbench core clearly states that it requires at least Laravel 9.34.

But this is obviously not a testbench, but a composer issue, since both testbench and testbench-core packages are properly specifying their minimum versions. And this constraint gets applied in the case of testbench but not for testbench-core.

Anyway, thanks a lot for your help! 🙇‍♂️

[crynobone]

Testbench Core cannot have any constraints against Laravel Framework because the Framework itself requiring Testbench Core for Integration Tests.

[fulopattila122]

As far as I see it does 🤔 https://github.com/orchestral/testbench-core/blob/v7.9.0/composer.json#L39
And I think it's even very correct, due to the BC in 9.32

[fulopattila122]

Noooow I got it!! It's a dev requirement, which means that it doesn't apply in this case 🤦‍♂️
Sorry for bothering 😬