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 completion). The generator works best on releases with 5–30 tasks; smaller releases produce thin notes, and larger ones get summarised aggressively.

For a release that's still being shaped, run the generator a second time after you finish, re-running overwrites the draft, it doesn't append.

What it does

Open the release modal, 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 (improvement type).
  • Fixes, bugs squashed (bug type).

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 consumes 2 AI credits, see AI overview.

Editing the draft

The draft renders inside a Markdown editor. Edit anything. Sections you don't want, drop them. Tasks that shouldn't appear publicly (internal refactors, security details), delete those lines.

The draft saves to the release as releaseNotesDraft until you publish. You can leave it half-edited and come back later; nothing is sent 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.
  • In the in-app "What's new" modal that surfaces recent releases to your collaborators.
  • In any future external feed (RSS / changelog page) that reads from release.notes.

You can edit published notes at any time. The generator doesn't overwrite published notes on subsequent runs unless you explicitly re-publish.

What's next

  • For pulling user-facing language directly from inbound feedback: Convert feedback to task.
  • For cycle setup that determines what goes into a release in the first place: Releases.
Last updated