On the Available Updates (admin/reports/updates) page there are links beside each update to download the update and to view its release notes. The release notes link is helpful to see if there are any major changes to note before updating, or any additional steps that need to be performed (e.g. run update.php).
However, consider the following example: You have version 1.x-1.0.0 of a module installed. Version 1.x-1.0.2 is available. You want to update, so you click the link to view the release notes. There's nothing important to note, so you go ahead with the update. But version 1.x-1.0.1 of the module requires additional work in order to update properly. You don't see that however, as you only see the release notes for 1.x-1.0.2...
I propose linking to a page* that shows all of the release notes between the installed version of a project and the version you're updating to. That way you can see all necessary steps/information/notes related to the update you're about to perform.
* I'm not sure if such a page exists in GitHub (at least a quick search didn't show a way to do this automatically)...
Recent comments
Title: Simplenews 1.x-1.2.2 removes subscribers when using anonymous checkout with Ubercart Hello, I experienced an issue when updating Simplenews to version 1.x-1.2.2. My site...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled
Hi ian, so, in your case all the other admin pages work fine, including the status page, only admin/reports/updates fails? But you can access admin/reports? Weird... I...
Update Report thows "Access denied You are not authorized to access this page."
The File (Field) Paths module should be able to move existing files. I've not tested it, but the module description says: Retroactive updates - rename and/or move...
Moving from /files into subdirectories