In T196206#5550248, @Reedy wrote:

https://github.com/symfony/symfony/blob/4.0/composer.json and https://github.com/symfony/symfony/blob/4.4/composer.json have ^7.1.3
https://github.com/symfony/symfony/blob/master/composer.json (to be 5.0 I guess) has ^7.2.9
https://github.com/symfony/symfony/commit/d94d9d792c445240cbaf80c7b413795b71aff718 - I wonder if there's any specific reason to select 7.2.9 as the min supported PHP 7.2, that dates to 16 Aug 2018, well before that commit in May
Something for us to bare in mind when we come to bumping to PHP 7.2
On https://github.com/symfony/symfony/blob/3.4/composer.json#L19 we're good with ^5.5.9|>=7.0.8
But of course, we only require PHP 7.0.0. I suspect most people will have a newer point release... But it does mean our require-dev symfony/yaml will conflict
Filing a separate task
Re-stalling as we have nothing to do until we bump to 7.2 (do we have a task for that to bump this against)

We should query and finalise what version of PHP to support... Currently we have 7.0.0 in composer.json, that's going to be changed...

https://github.com/wikimedia/mediawiki/blob/56e2567/composer.json#L35
https://github.com/wikimedia/mediawiki/blob/ed8e939/includes/PHPVersionCheck.php#L98

Should we consider to use/set 7.2.9 (rather than 7.2.0) to match and not conflict with symfony's requirements?

Ping T216166