Closed derrabus closed 3 years ago
We won't retag the skeleton for older versions, but I'm fine doing this on 5.4 In practice this shouldn't matter since composer will always select the latest.
Okay, let's merge to 5.4 then.
In practice this shouldn't matter since composer will always select the latest.
That is correct. However, this constraint will be persisted in the composer.json file of every new Symfony application that will be created from the skeleton. If we discourage the use of older versions, I believe that letting new applications start with that constraint is a good way to document that.
I'm fine with this change. At the very least, it sends a "subtle" message in the right direction :)
Thank you @derrabus.
Following https://symfony.com/blog/upgrade-flex-on-your-symfony-projects
The blog article tells the world not to use Flex versions older than 1.17. I think it would be wise to update the skeleton to reflect this request.