Release notes automation: the best tools and how they work

The best options for release notes automation are GitHub's auto-generated release notes, Release Drafter, release-please, semantic-release, Changesets and git-cliff for developer changelogs, and AI tools such as ReleasePad, ReleaseRay and Engammo for release notes that customers and non-technical teammates can read. The free tools turn commits or pull request titles into a list of changes. Engammo writes a plain-language release note for every merged GitHub pull request and publishes it to a changelog page, widget and RSS feed, with nobody having to remember to post.

What release notes automation is

Release notes automation means the notes for a release are produced from what your team already does in Git, instead of someone writing them from memory at the end of a sprint. Every tool starts from one of three inputs: commit messages (release-please, semantic-release, git-cliff), pull requests and labels (GitHub auto-generated notes, Release Drafter, Engammo), or files contributors add to each PR (Changesets).

The second question is who reads the result. Developer changelogs list what changed, grouped into sections like Features and Fixes, in CHANGELOG.md or GitHub Releases. Product release notes explain the change in plain language for customers, product, support and sales, and need to be published where those people already look. Most free tools are built for the first kind; Engammo was built for the second.

Release notes automation tools compared

Vendors change plans and add AI features regularly, so check each product's current pricing before you decide.

Free release notes automation for GitHub

GitHub auto-generated release notes are the simplest starting point. When you draft a release, GitHub lists the pull requests merged since the previous release, highlights new contributors and links to the full diff. An optional .github/release.yml groups PRs into categories by label.

Release Drafter is a GitHub Action that keeps a draft release updated as each pull request merges, grouping PR titles by label through a YAML config. release-please, maintained by Google, reads Conventional Commits and keeps a release PR open with the version bump and an updated CHANGELOG.md. semantic-release releases on every qualifying merge and publishes through plugins such as npm and GitHub Releases. Changesets suits JavaScript and TypeScript monorepos, and git-cliff renders a changelog from your Git history through a fully customizable template.

All of these are free and excellent for engineers. The output is still a list of commit subjects or PR titles, which most customers will not read. For the details, see the best tools to generate release notes from GitHub pull requests and the best alternatives to Release Drafter.

AI tools for release notes

ReleasePad is a changelog with a GitHub App. On the Pro plan each merge becomes an AI draft, and nothing is published until you approve it. ReleaseRay works per release: you pick a range by tags, dates or PR numbers, and it writes drafts for engineers, internal teams and customers using your own OpenAI or AWS Bedrock keys.

Engammo is a GitHub App that automates the whole loop. When a pull request merges, it reads the title, description, labels and a trimmed summary of the changed files, writes a short plain-language note with AI, tags it from your PR labels (features, fixes, breaking changes, security, docs and more) and publishes it within seconds.

• A hosted public changelog page that updates itself after every merge
• An embeddable widget added with one script tag, in English, Italian or Spanish
• An RSS feed and read-only public JSON endpoints for your docs or app
• Tag-based release notes that compile every change between two Git tags into one versioned note
• FAQ sync to a Kommander assistant, so it can answer questions about what shipped

Every note can be edited, regenerated or hidden. Engammo does not store your source code, only the generated note and PR metadata. Our overview of AI release notes generators for GitHub goes deeper on the AI options.

Proof: Engammo's own release notes

Engammo writes its own release notes. Every entry on engammo.com/releases was generated by Engammo from a merged pull request in our repository. It is the fastest way to judge what the output will look like for your team.

How to choose a release notes automation tool

• You want something free with no setup: GitHub auto-generated release notes.
• You want a draft release kept up to date on every merge: Release Drafter.
• You publish packages and want versions bumped automatically: release-please or semantic-release.
• You maintain a JavaScript monorepo: Changesets.
• You want to review an AI draft before anything goes out: ReleasePad or ReleaseRay.
• You want a plain-language release note for every merged PR, published automatically: Engammo.

These tools are not mutually exclusive. A common setup keeps release-please or semantic-release for versioning and uses Engammo for the customer-facing changelog. If you are choosing a changelog page or widget rather than automation, see the best changelog tools for SaaS teams, or follow our step-by-step guide to automating your changelog from merged PRs.

Engammo Starter is $29/month with a 14-day free trial, for up to 3 repositories with unlimited notes. Team, at $79/month, adds up to 10 repositories, Italian and Spanish translations, no Engammo branding and Kommander sync. See pricing.