Jordi Boggiano

Right, I'm guessing whatever builds the release sets `composer config platform.php 7.3.0` to ensure locked dependencies match that minimum PHP requirement. But then it's not added to the committed composer.json....

@boesing 40 seconds for check-platform-reqs sounds very extreme. If it is indeed due to plugins (can you check the time with --no-plugins?) then please run it like: `composer check -vvv...

That's the main chunk of what happens for every plugin. Sure there is some autoloading and all but that really shouldn't take 400ms unless you have many packages relying on...

Well, plugins need autoloading to work, so we ensure the plugin's dependencies and root package are autoloadable, because root package classes are sometimes needed for plugins to function (this is...

@boesing do you still experience this? Could you add some microtime checkpoints around https://github.com/composer/composer/blob/main/src/Composer/Plugin/PluginManager.php#L216-L261 to see how long that takes and if it is indeed the cause of the slowness...

@tobias47n9e do you have more repro instructions here? Where do you expect a .git folder exactly? Only in `vendor/company/internal-library`? Can you also reproduce this when running with `--no-plugins`? If you...

Well relying on named branches is fairly dangerous, as you can have major changes happening at any time. That's why we introduced the concept of branch aliases, so dev-main can...

The point of aliasing is to become compatible with numeric constraints. You don't really need an alias for named constraints because named constraints only ever match one exact name. I...

I guess that sounds ok.. Just the hardest bit as usual is naming it ;) But I'd rather keep it as static func on that class where it is tho...

After discussing this a bit I think something like this would be better: ``` { "compatible": { "acme/foo": "^2.5 || ^3.1" } } ``` That'd be converted to a conflict...