Jordi Boggiano

Looks good to me, thanks. I'd say feel free to add tests in the same PR..

Sorry but not sure what LEAP is, nor what we can do about it..

Curious why the shebang in installer wouldn't work for you.. But invoking with php installer explicitly should also resolve it

I believe this is fixed by #12149 already, will be in 2.8.2

Weird, I cannot repro this with the link like.. lrwxrwxrwx 1 seld seld 51 Oct 2 11:30 ~/.config/composer/config.json -> ~/.config/composer/config-real.json -rw-rw-rw- 1 seld seld 21 Jul 2 22:24 ~/.config/composer/config-real.json diagnose...

So this merge broke our build because for performance reason (to avoid recreating containers at every test) we suppress the tearDown client reset behavior, explicitly not calling the parent::tearDown(), and...

I'm not sure, I feel like it's a bug if this doesn't work, but I'd have to try and check why it's not working..

So I cannot repro this.. ```json { "repositories": [ { "type": "composer", "url": "https://MY_USER:[email protected]/test-repo/" } ], "require": { "foo/bar": "*" } } ``` Running `composer update -vvv --no-interaction` I get...

I agree this isn't really needed, considering doing this only requires this (or similar): ``` ->forceAttribute('a', 'rel', 'nofollow noindex noopener') ``` Of course this will apply to all links and...

It won't really fix anything because Composer will just use an older version of the bundle then that has no conflict. This should have been there from the start ideally,...