When viewing your currently-installed plugins, if you want to try to view changelogs for any that have available updates, you need to individually click on each plugin, load the details, then click the changelog/latest release link in there.
Then, to check the changelog of the next plugin with updates, you need to go back to the full plugins list, and scroll down to whatever the next plugin was (since going back to the full list resets your scroll position). It’s a pain.
Proposed solutions
I see a few potential solutions (though salves may be more appropriate for some):
If a plugin in the list has an available update (ie. if you would render an Update button), append the changelog link after the description, so it’s more easily accessible. (Or something similar in effect, like a button or clickable icon.) The ideal.
Offer a filter option in the “installed community plugins” screen to show only those with updates. Would be a nice QoL addition, making it easier to see what can be updated (which can be annoying with lots of plugins installed).
When clicking a plugin on the “installed community plugins” screen to open the plugin details, remember and restore the scroll position for when the plugin details screen is then closed.
Options 1 and 2 would complement each other nicely.
It’s becoming more challenging to keep track of all plugin updates. I propose that Obsidian reads a CHANGELOG file or release notes in each plugin repo that can be included in the settings UI similar to VS Code and JetBrains IDEs. Perhaps this could also be used for a global plugin updates feed that is broadcasted in Discord or Discourse.
Is there any simple method of viewing what has changed in a plugin’s update? The Obsidian UI will show, for example, “Found 9 plugins to update”, and I can scroll through the list in the UI, click on the plugin, then click on the Repository link to dig through any release notes, etc. Is that the recommended method, or am I missing something?
Hi, I just wanted to add this information as well. In github, where most of the community plugins appear to be coming from, it’s relatively easy to view code changes as well. The URL format is like this:
So for example, imagine you have the Database Folder community plugin installed at version (tagged) 2.8.1 and you can upgrade to version (tagged) 2.8.4. Then you can go to this URL and then “Files changed” tab to see the exact changes in the code that you will be installing: