Automated release notes,
drafted the moment you push.
Connect GitHub once. Every push to your release branch becomes a release note in language your customers understand, waiting for one click of approval. Nobody on your team writes it, and nothing goes out without you.
Automated drafting is part of Pro, $35 a month per product.
What are automated release notes?
Automated release notes are release notes drafted by AI from the record of what you shipped, your commits and pull requests, in place of a person writing each one by hand. Good release notes automation does two more things: it writes for customers, not for other engineers, and it leaves the decision to publish with you.
The release note nobody had time to write.
Shipping got faster. Telling customers did not. The work piles up at the end of the week, behind everything else, and the features you built stay invisible.
In a small team, release notes belong to whoever has a spare hour. There is no spare hour, so they are written late or not at all.
Turning fix: stream csv in chunks into something a customer cares about is real writing work, repeated every release.
A feature nobody hears about does not get used. Customers leave for things you already built.
From a push to a published note, with one step that needs you.
There is no pipeline to build and no webhook to wire. After setup, the only thing you do per release is read a draft and approve it.
Install the GitHub App, pick the repositories and the branch you release from. Two read-only permissions, no keys, no config file.
How the GitHub App worksEach push is read by AI, grouped into Feature, Improvement or Fix, and rewritten for the person using your product. You get an email when the draft is ready.
Read it, change anything, press approve. The note appears in your in-app widget and on your public changelog page at the same moment.
Where the note is publishedAutomatic does not mean generic.
Four settings shape every draft. Set them once and the notes arrive sounding like the rest of your product, so you stop making the same edits each release.
- Tone — professional, casual or technical.
- Language — written directly in English, Spanish, French, German, Portuguese or Italian, not translated afterwards.
- Detail — a one-line summary, a short paragraph, or the full explanation.
- Emoji — none, subtle or expressive, because there is no universally right answer.
Every draft stays fully editable, whatever the settings.
It drafts on its own. It never publishes on its own.
The fear with automation is a half-finished sentence reaching customers. That cannot happen here.
Every generated note is a draft until a person approves it. There is no setting to leave on by mistake.
Add [skip] to a commit message and it is left out of the draft. No ignore file to maintain.
Rewrite a line, merge two drafts into one, add a screenshot, or discard the draft entirely.
Approve now and set a publish time, so the note goes live with the feature and not before it.
The GitHub App asks for repository contents and metadata, read-only, on the repositories you choose. You can revoke it from GitHub at any time.
Plain commit messages work. Conventional Commits improve the grouping if you already use them.
Conventional Commits guideThree ways to automate, from zero setup to fully scripted.
Most teams only need the first. The other two are there when your releases do not start with a push to one branch.
Install it, choose a branch, and every push is drafted. This is the automation most teams want.
- ✓No pipeline changes
- ✓AI writes in customer language
- ✓Email when a draft is ready
Connect Claude Code or Cursor over the MCP server and add one rule to your project:
After merging a user-facing change, draft a release note for it in ReleasePad (product: Reports) as a draft and tell me the post id.
Never publish without asking.
On GitLab, Bitbucket or a custom release process, post a draft from your deploy job with the REST API:
curl -X POST "https://pro.releasepad.io/api/v2/manage/products/20/posts" \
-H "Authorization: Bearer $RELEASEPAD_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"title": "Export big reports as CSV",
"category_id": 64,
"draft": true,
"body": "Large reports now download without waiting..."
}'
All three need Pro. In every case the note is saved as a draft unless you choose otherwise.
Writing the note is half of it. Delivery is automated too.
A command-line generator hands you a Markdown file and stops. When you approve a ReleasePad draft, that one action puts the note everywhere your users look, and tells you who read it.
- Inside your product — the in-app widget shows an unread count to each user.
- On the web — a searchable public changelog page on your own domain.
- For machines — RSS and JSON feeds, a Markdown version for AI assistants, and webhooks for your own systems.
Views, unique readers and widget opens for every note, with CSV export.
Four ways to automate release notes, and where each one stops.
They all remove the blank page. They differ in who the output is written for and where it ends up.
| ReleasePad | GitHub’s generated notes | CLI generators | ReleaseNotes.io | |
|---|---|---|---|---|
| What starts it | A push to your release branch | Creating a release on GitHub | A command in your build | You create a release from an activity feed |
| What it writes | A customer-language note, rewritten by AI | A list of merged pull requests and contributors | A CHANGELOG.md from commit messages | An AI draft from the feed |
| Commit format | None required | None required | Conventional Commits expected | None required |
| Where it lands | In-app widget, public page, feeds | The GitHub Release | A file in your repository | Hosted page, widget and email, on paid plans |
| Price | $35 a month, flat per product | Free | Free, open source | From $39 a month per project |
CLI generators here means tools such as git-cliff and semantic-release. Competitor details are from each vendor's published documentation and pricing, checked in November 2026. If a file in your repository is all you need, the free generators are the right choice. More depth: three ways to automate release notes from GitHub, GitHub auto-generated release notes and ReleasePad vs ReleaseNotes.io.
What’s included in Free and Pro?
Publishing by hand is free. The automation on this page is part of Pro.
To try it with real releases.
- ✓Up to 20 posts on one product
- ✓Public changelog page
- ✓In-app widget
- ✓Write and edit in the editor
- ✓No credit card, no time limit
One plan. No seats, no usage tiers.
- ✓Unlimited posts and unlimited team members
- ✓AI drafts from your GitHub pushes
- ✓MCP access for Claude, ChatGPT and Cursor
- ✓REST API and webhooks
- ✓Analytics with CSV export
- ✓Your own domain, custom CSS, AI-readable Markdown
Full details on the pricing page. Open source projects and registered non-profits get Pro free on request.
Common questions
Built and maintained by the ReleasePad team · Last updated
Automated release notes are release notes that software drafts for you from the record of what you shipped, such as commits and pull requests, so nobody has to write each one from a blank page. With ReleasePad, a push to your release branch produces a draft in customer language, and you approve it before anyone sees it.
You install the ReleasePad GitHub App and choose a repository and branch. Each push to that branch is read by AI, grouped into Feature, Improvement or Fix, and rewritten in plain language. You get an email when the draft is ready, and one approval publishes it to your in-app widget and public changelog page.
No. Every generated note is saved as a draft and stays a draft until a person approves it. There is no auto-publish setting. You can edit, merge, schedule or discard any draft.
No. ReleasePad reads ordinary commit messages. If your team already uses Conventional Commits, the prefixes help it group changes more cleanly, but nothing requires them. Add [skip] to any commit message to keep that commit out of the draft.
Not natively. The automatic drafting works with GitHub. For other systems you can post from your own pipeline through the REST API, or have an AI coding agent save a draft through the MCP server.
GitHub's generator lists the merged pull requests on a GitHub Release, which suits developers reading your repository. ReleasePad rewrites the changes for customers and publishes them inside your product and on a public changelog page. We cover GitHub's own feature in our guide to GitHub auto-generated release notes.
The free plan covers writing and publishing by hand: up to 20 posts on one product, the public page and the widget. Automated drafting from GitHub, MCP access and the API are part of Pro, a flat $35 a month per product with unlimited team members. See pricing.
Ship on Friday. Find the release notes already drafted.
Start on the free plan and publish your first note by hand. Move to Pro when you want every push drafted for you: $35 a month per product, unlimited team members.