Jordi Boggiano

I think it'd be great to automate further if possible, maybe you can talk to @alcohol if you wanna help, I can help setup any credentials needed in the secrets.

We already push to two diff dockerhub ones. Official and ours. And then the AWS repo too. So I guess we could add gh.. But I'd like to ensure everything...

If you add files autoloading you will definitely need to run `composer dumpautoload` again, and then redeploy whatever files changed (this should only change things in vendor/composer/*) to your shared...

This explains it: ``` $ c why psr/http-message-implementation -t guzzlehttp/psr7 2.4.0 PSR-7 message implementation that also provides common utility methods └──laminas/laminas-httphandlerrunner 2.1.0 (requires psr/http-message-implementation ^1.0) └──composer/bug dev-master (requires laminas/laminas-httphandlerrunner 2.1.0)...

As you can see in "requires twig/twig 3.0" it seems your shell ate the ^ away. IIRC cmd or powershell tends to do that if not quoted somehow. Try ^^...

Marking this as a bug not because we can fix the shell parsing, but perhaps we could warn if on windows and require receives an exact version (especially if it's...

Yeah we'll need input from @Meryl here but the bottom line is the output indicates composer just received 3.0 as constraint.

Do you have xdebug installed? Could be a bug in the xdebug-handler restart? Try running with COMPOSER_ALLOW_XDEBUG=1 see if it fixes it.

Just FYI https://github.com/composer/composer/commit/740af2bdb16ce9249da9b7266ee49e67b679f336 should now warn - you can try after a `composer self-update --snapshot` see what happens..

Yes that does suggest it.. But I am still not sure where it vanishes, as this works fine here for me: ``` $ c req "twig/twig:^3.0" ./composer.json has been updated...