Jordi Boggiano

No what I mean is that if we merge/release this PR, a composer update would still then possibly upgrade to predis/predis 3.x if your requirements allow it, but it would...

> * For now I'm not sure if this option should be added to all commands that have auditing (similar to how `--audit-format` is implemented. I'd like input on that....

- repositories[0].package.name : The property name is required - repositories[0].package.version : The property version is required These are the errors, you have no name or version so that package you...

> I don't want this, where did you read that? ``` "dist": { "type": "path", "url": "../depend" } ``` This tells me that's what you're trying to achieve, but whatever..

No these are required for the dependent package to be installable, but the validate errors are about your root package, so the name & description keys at the top level...

It has to be specified in both places. One defines the package and the other requires it to be installed

IMO the better way to do this would be to do `composer config -g preferred-install dist`, so that the value applies to the entire system/machine, which is usually a good...

I see, then go ahead and abuse COMPOSER_AUTH I guess..

Great stuff overall, thanks for picking this up! :)

Ah an interesting problem came up here https://github.com/symfony/symfony/pull/57653/files#r1671760696 - what if the enum class is not defined? Should it make an empty value set then? Or error loudly but in...