GitHub-native release pipeline

Ship release notes that sound like your best product marketer, not your raw commit log.

ReleaseNotes.ai watches pushes, tags, and PRs, turns them into readable drafts with AI, and helps your team publish polished releases plus public changelog pages in one review flow.

Indie devs, SaaS teams, and maintainers shipping on GitHub.
Readable releases without a manual copywriting pass every week.
GitHub App, Next.js, Prisma, Postgres, Fireworks AI.

acme/platform

DRAFT
release notev1.8.0
Summary

New self-serve billing, faster dashboard queries, and a simpler onboarding flow for new repositories.

Technical
  • Refactored repo sync jobs and caching strategy.
  • Improved webhook deduplication for tag events.
  • Fixed release publishing edge case on retries.
git push origin main
tag: v1.8.0
PRs: #184, #191, #204
Draft
Review
Publish

Review once, then send the final version to GitHub Releases and your public changelog page.

GitHub App installs with repo-level scope
AI-generated drafts from real release activity
Review before publish, not after the mistake
Hosted changelog pages for every repo

A release flow that starts in GitHub and ends in a polished changelog.

The point of the product is not more release management busywork. It is fewer manual summaries, fewer missed details, and a cleaner handoff from engineering to the people who read your updates.

01

Install the GitHub App

Connect one repo or your whole org in minutes, then choose which projects should generate releases.

02

Push, tag, or merge

ReleaseNotes.ai listens to the GitHub events your team already uses, then collects commits, PRs, and context automatically.

03

Review an AI draft

Fireworks AI turns raw activity into a readable release note with technical and non-technical summaries.

04

Publish everywhere

Ship the final version to GitHub Releases and expose it on a public changelog page without duplicating work.

From commit noise to a release your customers can actually scan

Group changes by theme, explain impact in plain language, and still preserve the technical detail your internal team needs.

Technical and non-technical summary blocks
Draft-first workflow before anything goes public
Consistent structure across every release

A workflow shaped around installs, webhooks, and repos instead of copy-paste docs

The product starts where your release data already lives: GitHub App installs, Octokit access, pushes, tags, and pull requests.

GitHub login and repo-based access
Webhook ingestion for push and release activity
Direct publishing back into GitHub Releases

Every repo gets a polished changelog page your team does not have to maintain manually

Once approved, each release becomes part of a public timeline at `/changelog/owner/repo`, ready for customers, prospects, or internal teams.

Hosted release history per repository
Fast skim layout for each update
A cleaner alternative to scattered markdown files

Small details that make the workflow feel operational on day one.

01Multi-project support
02Draft and publish lifecycle
03Repo ownership per GitHub install
04LLM-generated changelog sections
05Review-friendly editor surface
06PostgreSQL release history
Ready to ship better releases?

Transform your release workflow today.

Join teams who have automated their release notes and freed up hours every week.

Questions teams usually ask before they trust release automation.

Does it write directly to GitHub Releases?

Yes. The intended workflow is draft first, then a reviewer approves and publishes the final text back into GitHub Releases.

Can I use it for internal-only projects?

Yes. Public changelog pages are optional. Teams can keep the workflow private and still use the review and publishing pipeline.

What triggers a release draft?

Pushes, tags, and related repository activity are the main triggers in this MVP. The webhook layer can expand later as needed.

Why a GitHub App instead of another dashboard integration?

A GitHub App gives repo-scoped installs, webhook delivery, and authenticated publishing, which matches the release workflow more cleanly.

Let GitHub activity become polished release communication by default.

The MVP is built for teams who want clean release notes without bolting another manual writing step onto every deploy.