not in favor of using a filter to hide the UI on a page that is not likely to be accessed by users who have the ability to update core

I’d like to point out that this is not an accurate summary of my current stance as expressed on the ticket. From my comment:

” The update page is ONLY accessible to those WITH the update_core capability.

It’s not that the users are unlikely to access the page with the new UI. It’s that this page is only accessible by Administrators (by default), and these users actually should be presented with this information.

By default, only Administrators have this capability. If a site owner does not want auto-updates for major versions, then they should use the constant to enforce only minor updates (or none, if desired).

Rather than allow this UI to be hidden entirely, I’m arguing that it would potentially be a better user experience to instead disable the form when auto-update behavior is being controlled by the constant and inform the user (who will always be a trusted individual because they have the update_core capability) of how the site will behave when new major and minor versions become available for auto-updating.