Update module currently handles at least two separate things:
1. Provides security and bugfix release notifications to site owners.
2. Provides the UI to allow site owners to update their sites via uploading tarballs.
Additionally, the automatic updates initiative is adding additional infrastructure to enable unattended updates.
There will be many sites that would like to have notifications for security releases and bugfixes, but have no intention of managing their code base via the UI, so we should consider splitting these two functions into different modules.
Fixed
11.0 🔥
update.module
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
With 📌 Deprecate/remove the ability to update a module from a URL and authorize.php Active and all child issues (and 📌 Rename update module back to Update Status Active ) all fixed, this is now separated. We're back to core only providing point #1 from the summary. Calling this plan fixed.
Automatically closed - issue fixed for 2 weeks with no activity.