May be something to do after 1.39 is branched... But composer 1.x is EOL, and there's probably no good reason to continue supporting it for much longer
https://blog.packagist.com/composer-2-0-is-now-available/
As for Composer 1.x, it is now more or less EOL.
^ since October 2020
https://www.mediawiki.org/wiki/Composer should be updated when appropriate.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Stop supporting composer 1.x | mediawiki/core | master | +55 -1 K |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Reedy | T316556 Newer doctrine/dbal requires composer-runtime-api: ^2 | |||
| Resolved | Reedy | T316558 Drop support for composer 1.x |
Change 990342 had a related patch set uploaded (by Reedy; author: Reedy):
[mediawiki/core@master] ComposerInstalled: Stop supporting composer 1.x packages
Change 990342 merged by jenkins-bot:
[mediawiki/core@master] Stop supporting composer 1.x
https://blog.packagist.com/shutting-down-packagist-org-support-for-composer-1-x/
Key Dates:
February 1st, 2025: Composer 1.x metadata will become read-only. No new packages or new versions will be visible for Composer 1.x users after this date. August 1st, 2025: Composer 1.x metadata access will be entirely shut down. Attempting to update packages using Composer 1.x will no longer work.