stacklok / stacklok/toolhive-studio
[Story] Display changelog in GUI
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 167
- Forks
- 24
- Avg merge
- 11h 32m
- Merged PRs (30d)
- 91
Description
Story Title
As a user, I would like to learn about new features, and I would like to know why I had to restart ToolHive Studio
Description
As a user, I would like to learn about new features, and I would like to know why I had to restart ToolHive Studio.
This could be as simple as a popup window with the title "What's new" and just displaying the same changelog we have in GitHub
Acceptance Criteria
- after a new update is installed, we display the changelog to the user
Target Release
v0.2.0
Priority
Low
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the GUI update-installation flow and how the application handles a restart after an update. Then trace where the GitHub changelog can be obtained and how GUI windows or popups are presented. Done means that, after an update is installed, the user can view the changelog in a "What's new" display.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100