@brianteeman Reason is that in https://update.joomla.org/core/nightlies/next_major_extension.xml we have <php_minimum>8.1.0</php_minimum>. So for the nightly builds it has to be fixed here: https://github.com/joomla/update.joomla.org

@HLeithner As I remember, we had decided not to enforce the increased database requirement for 6.0, so it would only need to fix the <php_minimum>, right? Or should we also adjust <supported_databases>? And we would have to fix it in TUF for 6.x, too, right?

I made a PR joomla/update.joomla.org#415

Suggest this stays open until that is merged so we dont get other reports

I've merged joomla/update.joomla.org#415 . Thanks.

Could you check if it is solved? If not, we have to change it on some other place, too. Not sure if the update model takes it from the fetched update or if it's hard-coded.

that didnt change anything inside joomla 5.4 although my reading of the code suggests that it should have

With these XMLs we often observe that it takes a while until changes arrive on a client, possibly due to cloudflare caching.

Maybe you can check https://update.joomla.org/core/nightlies/next_major_extension.xml in your browser?

ah good point - will check again later. Although my browser (on the same IP as the test server) does show the updated xml

Yes, same as I had observed in past. Let's wait and see later.

Please check and test #45911

Closing as having a pull request. I've already tested it with success, so only 1 more test needed. And of course it will be merged up into 6.0-dev after it has been merged into 5.4-dev.