Conflicts with Symfony console about cli

[jasonvarga]

Can you post the output of composer global why symfony/console ?

[jonassiewertsen]

composer global why symfony/console

mnapoli/silly       1.8.0   requires   symfony/console (~3.0|~4.0|~5.0|~6.0)
symfony/var-dumper  v6.0.3  conflicts  symfony/console (<5.4)

composer global why symfony/var-dumper

tightenco/collect  v8.83.2  requires  symfony/var-dumper (^3.4 || ^4.0 || ^5.0 || ^6.0)

composer global why mnapoli/silly

laravel/valet  v2.18.9  requires  mnapoli/silly (^1.0)

I hope this helps.

I haven't looked into it any further and did use composer create-project statamic/statamic instead, in case anybody is looking for a workaround.

[richdynamix]

I also have similar output and same issue -

laravel/installer    v4.2.10  requires   symfony/console (^4.0|^5.0|^6.0)
laravel/vapor-cli    v1.36.0  requires   symfony/console (^4.2|^5.0|^6.0)
mnapoli/silly        1.8.0    requires   symfony/console (~3.0|~4.0|~5.0|~6.0)
symfony/translation  v6.0.5   conflicts  symfony/console (<5.4)
symfony/var-dumper   v6.0.5   conflicts  symfony/console (<5.4)
symfony/yaml         v6.0.3   conflicts  symfony/console (<5.4

[jasonvarga]

Assuming there are no relevant breaking changes in symfony/console and symfony/process, we can just update our composer.json to include ^6.0.

[jesseleite]

^ Updated dependency in that PR there. Looking back at changelog, I don't think I see any breaking changes that should affect us.