When the plugin manager of Jenkins shows that there are updates available, I usually click through the list and look at the release notes of each plugin. This currently requires two clicks per plugin: one click to follow the link to plugins.jenkins.io, and then another click to select the "Releases" tab there; and the version shown at the top of the list there might not be what the plugin manager is offering. It would be more convenient if the table of plugin updates linked directly to the release notes of the specific version that is available.

For example, core/src/main/resources/hudson/PluginManager/updates.jelly currently formats HTML:

<div><a rel="noopener noreferrer" href="https://plugins.jenkins.io/analysis-model-api" class="jenkins-table__link" target="_blank">Analysis Model API<span class="jenkins-label jenkins-label--tertiary" style="margin-left: 1ch;"><span class="jenkins-visually-hidden">Version</span>
                              12.9.1
                            </span></a></div>

That could instead link to the specific version https://plugins.jenkins.io/analysis-model-api/releases/#version_12.9.1, or have two separate links:

<div><a rel="noopener noreferrer" href="https://plugins.jenkins.io/analysis-model-api" class="jenkins-table__link" target="_blank">Analysis Model API</a>
<a rel="noopener noreferrer" href="https://plugins.jenkins.io/analysis-model-api/releases/#version_12.9.1" class="jenkins-table__link" target="_blank" style="margin-left: 1ch;"><span class="jenkins-label jenkins-label--tertiary"><span class="jenkins-visually-hidden">Version</span>
                              12.9.1
                            </span></a></div>

although this extra link would require extra TAB keypresses from keyboard users.

I think the cleanest way to do this would be to add the URL of the release notes as a new property of each plugin in https://updates.jenkins.io/current/update-center.json, then make PluginManager.java and updates.jelly format that. That could affect the network egress costs of updates.jenkins.io, though.