Make major upgrades upgrades quicker by modifying the composer.json for us

[aaronbushnell]

When upgrading from Craft 3 to 4 and 4 to 5 Craft provides a (very handy!) "Craft X Upgrade" utility panel. One of my biggest complaints about upgrading to the next major version is hand-changing every package in my composer.json based on the plugin compatibility list in this area.

Which makes me wonder—if Craft knows what is "Ready". And if all of my plugin versions are identified in this area. Then why can't Craft do this part for me?

It's not the worst thing in the world to do, but it is pretty cumbersome if you oversee a fair number of sites going from one major version to the next.

[brandonkelly]

Just released Craft 4.16.6, with an improvement to the Craft 5 Upgrade utility: the “Ready to upgrade?” pane now has a “Prep composer.json” button. When pressed, a modal window will be shown with the project’s composer.json file, with craftcms/cms and plugin package constraints updated to the latest known Craft 5-compatible versions.

[aaronbushnell]

This is AMAZING. Thanks, @brandonkelly!