Clear, customer-facing release notes are drafted automatically from the team's merged changes, so a consistent changelog ships with every release.
Typical results
Minutes
from merge to publishable changelog
100%
of releases ship with notes
0
changelogs skipped or postponed
Auto
drafts written from merged changes
Figures reflect typical results for this kind of automation.
The challenge
Writing changelogs was a manual chore that the team often postponed, so customers rarely heard about new improvements.
Before and after
Time to produce release notes
−89%Releases shipping with a changelog
2.5×The automation
We automated a flow that, when changes are merged for a release, gathers them and drafts plain-language release notes a team member can review and publish in minutes.
How it works
- 01
Changes merged
Merging the changes for a release triggers the flow automatically.
- 02
Changes gathered
Everything going into the release is collected in one place.
- 03
AI drafts the notes
Technical changes become plain-language, customer-facing release notes.
- 04
Quick human review
A team member polishes and approves the draft in minutes.
- 05
Changelog published
Every release ships with consistent notes — customers stay informed, effort stays near zero.
Starts from
- Merged changes
Delivers
- Release notes
The impact
The team now ships a consistent changelog with every release instead of skipping it, keeping customers informed with almost no effort.
Questions about this automation
Where does the automation get the list of changes?
It reads the merged pull requests, commit messages and linked issue titles for the release from the code repository and the issue tracker. Internal-only items, such as refactors or dependency updates, are filtered out by labels, so the draft covers only changes a customer would notice or care about.
Who reviews the release notes before they are published?
A product manager or another team member gets the draft by email or Slack with a link to edit it. Nothing goes live until that person approves it. After approval, the notes are published to the changelog page and can also go out as an in-app message or a customer email.
Can the notes match our own tone and format?
Yes. The AI step works from a style guide and a few past release notes, so headings, wording and the order of new features, improvements and fixes stay consistent. Simple automations like this are usually live within days, because they read from the repository and tracker already in use.