[6.1] Understand how new version installed is shown

[llaville]

With version 6.1.0 PHP_CompatInfo (and PHP_CompatInfoDB 3.17.0) both are removed deprecated composer/package-versions-deprecated composer plugin, and use now the Runtime Composer v2 utility.

In practice, that means when you get help of CompatInfo, you will get the version installed (even if in current development) and when you'll ask for long version you'll get the hash of commit corresponding to version.

See example in screenshot :

PHP_CompatInfo

PHP_CompatInfoDB

[llaville]

Another example with PHP_CompatInfoDb 3.18 that have just started its development

[remicollet]

With version 6.1.0 PHP_CompatInfo (and PHP_CompatInfoDB 3.17.0) both are removed deprecated composer/package-versions-deprecated composer plugin, and use now the Runtime Composer v2 utility.

So why, during composer install, I got:

  - Installing composer/package-versions-deprecated (1.11.99.4): Extracting archive
composer/package-versions-deprecated contains a Composer plugin which is currently not in your allow-plugins config. See https://getcomposer.org/allow-plugins
Do you trust "composer/package-versions-deprecated" to execute code and wish to enable it now? (writes "allow-plugins" to composer.json) [y,n,d,?] y

P.S. probably pulled by some other libraries (doctrine/dbal and doctrine/orm)

[llaville]

Confirmed with command composer why composer/package-versions-deprecated

[llaville]

Not yet in effect, because composer 2.2 compatible releases

• is available for doctrine/dbal (3.2.1) - see doctrine/dbal@6cb7287
• not yet available for doctrine/orm - see doctrine/orm@72edfbc

[llaville]

Available now in doctrine/orm since v2.10.5