Martin Herndl

I grabbed the phar artifact and could verify this which is good I guess ```sh php phpstan.phar --version PHPStan - PHP Static Analysis Tool 1.8.x-dev ```

`InstalledVersions::getPrettyVersion('phpstan/phpstan')` seems to be doing the trick, I see no commit there. Did I get you right - should I try that out and use the Composer 2 API instead?...

hmm this was looking promising, but `php phpstan.phar --version` shows `Version unknown` :/

I think this is looking good now, even better than before this PR since it also works on my local machine :) I hope it also still works on tags...

hmm weird, did you change the lockfile for a specific reason? there are now some packages still inside that are not required by anything. but they'd be removed with the...

yep, it's not a problem. I'll just open a PR to update paratest and there e.g. `composer/package-versions-deprecated` will be removed from the lockfile. the new paratest brings back `jean85/pretty-package-versions` in...

Oh no, I found another thing. I was completely ignoring the composer integration test already because it's red and missed that this PR most likely made it worse: ``` PHP...

Nice, I didn't have time to debug it yet unfortunately

I guess I'd try using xdebug here, in case you didn't do that already.

We're also affected by this and this PR seems to be getting quite some attention. Is there any way to drive this forward? Are you fine with somebody taking over...