Issue Unexpected update of composer to 2.0-dev

[andre.spindler]

I get unexpected errors when maintaining composer based applications on my web server.
Composer is now version 2.0-dev (Composer version 2.0-dev (2.0-dev+40a35abb9423e16f8bafcb1ed1b7e027881b0422) 2020-04-10 10:24:43) on Plesk onyx.

When was this update published? Why do we get this update?
Version 2.0-dev is also no official release. The latest version is 1.10.5 2020-04-10 sha256 d5f3fddd0be28a5fc9bf2634a06f51bc9bd581fabda93fee7ca8ca781ae43129
Seems like plesk is running a public alpha test with all of its customers. Rolled out during easter weekend.
It is also possible that the updates are not maintained at all by plesk and we have some strange automatic deployment here.

Also the Obsidian realease is affected: Question - Composer v2.0.0

 

[Remy Vaartjes]

Yes, this is very annoying and unusable. Please fix this. This is the wrong version.

After each automatic Plesk update we have to perform a manual update of composer:
/opt/plesk/php/7.2/bin/php /usr/lib64/plesk-9.0/composer.phar self-update

This rolls it back to the official version:
Composer version 1.10.5 2020-04-10 11:44:22

Strange that this is slipping through, has been a problem now for a couple of weeks.