disagree on having the 'newest' php set as the default..
that's going to cause more issues than it solves..
that said, having new php releases, eg php 8.6 later this year, automatically added to the system and enabled in all packages does make sense.. saves admin a job..
just never set it as the default version, if a customer wants to use it on a new site, or just test to see if it breaks their current site, they can manually set their website to use it.
the only reason i can see for a packages default version being changed without admin intervention is when the packages current default version goes out of support, then it makes sense to bump the default for that package to the next version up.
