The editor
The release body uses a rich text editor. Use the toolbar, or type Markdown and it converts as you go:
Pasting Markdown from another tool works too. It converts on paste.
Images
Drag an image into the editor, paste it from your clipboard, or use the toolbar to upload one.Media embeds
Paste a link on its own line and Onset embeds the player:- YouTube
- Loom
- Vimeo
Change lists
For releases with many small changes, use the change list instead of stuffing everything into the body. Each entry is a change type plus its content. There’s no separate title field. You pick the type from a dropdown and write the change itself in the editor, with the same formatting available as the main body. Entries can be reordered by dragging. A good pattern: the body explains why this release matters, the change list covers everything that changed.Change types
Onset ships with a default set, following the Keep a Changelog convention:Customize the types
The list isn’t fixed. Go to Settings → Workspace → Releases to add your own types, rename existing ones, change their color, or reorder them. Each type has a title and a color, and the order you set is the order shown in the editor dropdown.Writing tips
- Lead with what the customer can now do, not what you built.
- Link to the relevant docs page rather than re-explaining it.
- Publish one release per meaningful change rather than a weekly dump. Your feeds and notifications get more useful that way.
- If you’re stuck on the first draft, the AI assistant can generate one from your GitHub, Linear, or Jira activity.