Release notes generator
Turn a completed release into a clean markdown draft of features, improvements, and fixes. You edit, you publish.
The release notes generator drafts user-facing notes for a release based on the tasks it shipped. You review, edit, and publish. Frostbyte never auto-sends anything.
When to use it
Run it after marking a release as completed, or close to it. The generator works best on releases with 5 to 30 tasks: smaller releases produce thin notes, and larger ones get summarised aggressively.
If the release is still being shaped, run the generator again once you finish. Re-running overwrites the draft rather than appending to it.
What it does
Open the release modal and click Generate notes. Frostbyte sends the release's tasks (titles, types, descriptions) to an LLM and returns a draft structured into:
- Features: new capabilities, drawn from
feature-type tasks. - Improvements: refinements to existing capabilities, from
improvement-type tasks. - Fixes: bugs squashed, from
bug-type tasks.
Within each section, related tasks are grouped and rewritten from internal-task language ("Fix the broken assignment reorder") into user-facing copy ("Reordering task assignments now works correctly").
Cost
Each generation typically uses about 2 AI credits. Actual usage varies with the number of tasks and the length of the notes. See AI overview.
Editing the draft
The draft opens in a markdown editor. Edit anything. Drop sections you don't want, and delete lines that shouldn't appear publicly, like internal refactors or security details.
The draft stays on the release until you publish, so you can leave it half-edited and come back later. Nothing is visible to anyone until you click Publish.
Publishing
Publishing makes the notes part of the release record. They appear on the Public roadmap when the roadmap is enabled and the release is flagged public, and in the in-app "What's new" modal that surfaces recent releases to your collaborators.
You can edit published notes at any time. Re-running the generator won't overwrite published notes unless you publish again.
What's next
- For pulling user-facing language directly from inbound feedback: Convert feedback to task.
- For deciding what goes into a release in the first place: Releases.