Book a demo

Steps

Search the web for our last changelog entry
Search GitHub for merged pull requests since that date
Search for completed issues and tasks since that date
Think and detect the top 1-3 themes across changes
For each theme, find additional context and details
Generate the formatted changelog
With the data found generate the changelog with our template, filtering out internal or irrelevant topics.

What it is

The Release Note Writer workflow automatically creates your changelog by gathering all your merged pull requests and completed issues, organizing them into meaningful themes, and translating technical changes into user-friendly release notes. It's like having a technical writer who knows exactly what shipped and why it matters.

What it solves

Writing release notes is tedious busywork that nobody wants to do. Product managers dig through GitHub trying to remember what merged. Engineers translate their own technical work into user language. Marketing waits around for someone to tell them what actually shipped. The whole process takes an hour of everyone's time and usually results in either overly technical jargon or vague "bug fixes and improvements."

The Release Note Writer eliminates the manual archaeology. It pulls everything together automatically, identifies the important themes, and writes notes that actually explain what users care about—not what branch got merged into what.

How it works

Super starts by finding your last changelog entry so it knows where to pick up. Then it searches GitHub for merged PRs and Linear for completed issues since that date. It analyzes all the changes to detect the major themes—maybe you shipped three features related to notifications, or fixed five bugs around file uploads.

For each theme, it gathers additional context and details, then generates a structured changelog organized by impact: major updates first, then new features, improvements, and bug fixes. The language is user-focused, not developer-focused, so your customers understand what changed and why they should care.

How to use it

Run the workflow whenever you're ready to publish release notes—whether that's weekly, bi-weekly, or after major releases. You can specify a date range or just tell it "since last release" and let it figure out the rest.

The workflow generates a draft changelog that you can review, tweak if needed, and publish. Connect it to your changelog platform (like Sanity) to automate publishing, or use the output as a starting point for more detailed release announcements. Perfect for keeping customers informed without the manual grind of tracking down what actually shipped.