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
Thanks!! Easiest for me to just give permission for anon users to see the admin theme. That worked. It's just for this one page.
Link field in a Content Type is malformed for annonymous user- Permission issue?
It looks like the screenshot of what you show it should look like is the admin theme whereas what they see is the front end theme. By default, such users won't have permissions to see the...
Link field in a Content Type is malformed for annonymous user- Permission issue?
I've added a new recipe. The recipe has no PHP code. It has two module dependencies (one of those depends on another contrib module and both depend on core modules that are normally enabled)...
The Future of Configuration Recipes for Backdrop CMS