Jordi Boggiano

Seems somewhat related to #12158 - I assume given the /data path that you run composer inside docker? The question is where is /data/www/.composer/cache located, is that a mounted path...

Added some warnings/errors, I don't think we can do much more than that but hopefully it helps diagnose the problem quicker.

Bearer auth is currently only supported for API requests, so if you install with --prefer-dist I believe it should work. We don't support it for git but it's good to...

Sounds reasonable to me if you want to send a PR :)

No clue what could cause this sorry. Maybe you have an alias defined for `composer`? Try running these and sharing the output ``` alias | grep composer which composer ```

Where is this -a coming from then? Can you check the source of your composer bash completion script see if there's anything containing -a in there?

Have you tried to set an extra.branch-alias in package-1 so that dev-master is seen as 1.2.x-dev or 1.x-dev? That should solve it I believe.

Sorry not sure what you are implying. It works but not fully? If not then what/why?

The fact that is_readable is true there is really messed up, but yeah we'll have to fix this and make sure we ignore errors.

Oh.. new dependencies in v6, I hadn't noticed that until now. Not a fan of that, but so it goes. On the other hand Composer can probably stick to v5...