Summary
When a new version of the ToolHive UI is available, the update UI should include a direct link to the release notes so users can review what's changed before deciding to upgrade.
Motivation
Right now, the update flow asks you to download and install a new version without giving you any easy way to see what's actually in the release. If you're on manual update mode, you see a box with a download button, but no context about what you're downloading. For auto-updates, the confirmation modal has the same gap.
Linking to the changelog before the user commits to an update is a small change that builds trust and helps users make informed decisions about when to upgrade.
Proposed behavior
Manual updates: Add a "View release notes" link alongside the existing download button in the update notification area.
Auto-updates: Add a "View release notes" link in the update confirmation modal, so users can review changes before confirming.
The link should point to the corresponding GitHub release (e.g., https://github.com/stacklok/toolhive-studio/releases/tag/vX.Y.Z).
Related: improve the release notes themselves
Since these release notes will now be more visible to end users, it's worth investing in making them more polished. The current GitHub releases use basic auto-generated notes. The main toolhive repo has a Claude Code skill in progress for generating better-formatted release notes. We should consider adopting the same skill or approach in toolhive-studio for consistency across both repos.
Implementation notes
- The version number for the pending update is presumably already available in the update check logic, so constructing the GitHub release URL should be straightforward.
Summary
When a new version of the ToolHive UI is available, the update UI should include a direct link to the release notes so users can review what's changed before deciding to upgrade.
Motivation
Right now, the update flow asks you to download and install a new version without giving you any easy way to see what's actually in the release. If you're on manual update mode, you see a box with a download button, but no context about what you're downloading. For auto-updates, the confirmation modal has the same gap.
Linking to the changelog before the user commits to an update is a small change that builds trust and helps users make informed decisions about when to upgrade.
Proposed behavior
Manual updates: Add a "View release notes" link alongside the existing download button in the update notification area.
Auto-updates: Add a "View release notes" link in the update confirmation modal, so users can review changes before confirming.
The link should point to the corresponding GitHub release (e.g.,
https://github.com/stacklok/toolhive-studio/releases/tag/vX.Y.Z).Related: improve the release notes themselves
Since these release notes will now be more visible to end users, it's worth investing in making them more polished. The current GitHub releases use basic auto-generated notes. The main
toolhiverepo has a Claude Code skill in progress for generating better-formatted release notes. We should consider adopting the same skill or approach intoolhive-studiofor consistency across both repos.Implementation notes