Releases and outputs
Generating, editing, regenerating and downloading the thirteen announcement formats.
The thirteen outputs
Every release can generate thirteen announcement formats, each written natively for its channel: the Discord post is short with bullets, the thread leads with a hook, the press release has a proper structure.
- For your product: Customer changelog, Release notes, and Plain English, a version for readers who don't speak developer.
- For your team and community: Standup (a spoken update for the morning meeting), Discord announcement, Email newsletter.
- For the wider world: Blog article, X thread, LinkedIn, Reddit, Facebook, Product Hunt update and Press release.
Generate only what you need; each generation spends tokens separately.
Editing and regenerating
Click into any line to edit it directly. The assistant bar rewrites a whole output with one tap ("Shorter", "More professional") or a custom instruction ("mention the iOS app", "make the last section friendlier"). Rewrites spend far fewer tokens than full generations.
A green dot on a tab means that output has been generated; hollow means not yet.
The change list is yours
The left panel shows what Shipnote found: commits and pull requests grouped into categories, with internal changes (refactors, chores, tests) unticked by default. Tick or untick anything, and add manual changes with the text box for work git can't see. Regenerating uses the current selection.
Renaming, discarding, downloading
- Rename by clicking the title in the editor, or via the ⋯ menu on the releases list. The new title flows to your public page and feed.
- Discard removes a release permanently, always behind a confirmation.
- Download any output as Markdown, or open it print-ready for a one-click PDF: for the board deck, the wiki, or anywhere else no integration reaches.
Publishing, precisely
Publish opens a picker listing your public page and every connected destination. Each message destination can carry any generated copy (send the Release notes to Discord if you like), and JSON destinations receive the whole release. Oversized copy is flagged before it floods a channel, and destinations that already received this release show when they got it.