Stop shipping in silence.

changelogfa.st turns every merge into release notes for your team, your boss and your users — each in their own words. You type nothing.

Your workflow
Send
aupdate
via
every
What gets sent
#product
C

changelog-botAPPv2.8.0 · just now

Auth hardening & realtime stability

  • • OAuth now runs authorization-code + PKCE — blocks code interception. Closes PROJ-132.
  • • Worker heartbeat race fixed — no duplicate jobs after a redeploy.
  • • WS reconnect: exponential backoff + jitter.
  • • Dark mode toggle (PROJ-128), Settings → Appearance.

2 commits filtered out (docs, chore)

Written from your commits & tickets. You typed nothing.

Set up in 30 seconds · 1-day trial · cancel anytime

Plugs into the 8 tools you already ship with

GitHubGitLabGiteaLinearJiraSlackGmailWebhook

New · Workflow builder

Set up your release notes in one sentence.

No forms, no YAML. You build the whole workflow as a sentence you can read out loud — click any colored word to change it.

  • Pick a trigger — a GitHub release, a merge, or a daily recap.
  • Choose the voice — executive, technical, or your own.
  • Send it anywhere — Slack, email, a webhook, your public page.
  • Enrich it with Linear or Jira tickets — automatically.
Your workflow
On everyGitHub release
ofchangelogfa.st
sendaexecutiverelease note to#changelogfast
+ channel
enriched withlineartickets

Sound familiar?

You shipped at 6pm. The release notes took until 8.

First you wrote them for your team. Then again, simpler, for your users. Then again as a 3-line recap for your boss. Same release, three rewrites, by hand — every single time you ship.

Or you connect your repo once, and never write a release note again.

Watch it work

Same commits. Same tickets.
Three finished release notes.

A real run, end to end: what your repo looks like after a sprint — and what every audience receives 60 seconds later.

The input — what your repo looks like after a sprint

6 commits since last release

feat: [PROJ-132] OAuth login with PKCE

fix: worker heartbeat race condition

feat: websocket reconnect with backoff

feat: [PROJ-128] dark mode toggle

docs: update migration notesnoise · filtered

chore: bump dependenciesnoise · filtered

2 linked Linear tickets

PROJ-132Urgent

Login fails on public Wi-Fi — auth code can be intercepted

Reported by 3 customers

PROJ-128

Dark mode

Most-requested feature · 214 upvotes

changelogfa.st reads commits + tickets, filters the noise, then writes one version per audience

For your engineers

Slack · #engineering · technical

#engineering
C

changelog-bot APP

v2.8.0 — auth hardening & realtime stability

  • • OAuth now runs authorization-code + PKCE — blocks code interception on shared networks. Closes PROJ-132.
  • • Worker heartbeat race fixed: state transitions behind a mutex. No more duplicate jobs after a redeploy.
  • • WS reconnect: exponential backoff + jitter — no thundering herd on network blips.
  • • Dark mode toggle (PROJ-128), Settings → Appearance.

2 commits filtered out (docs, chore)

For your customers

Email · plain-English

To: customers

Dark mode is here — and sign-in got safer

Hi — three things shipped this week:

🌙 Dark mode. Your most-requested feature. Turn it on in Settings → Appearance.

🔒 Safer sign-in. Extra protection when you log in from café or airport Wi-Fi.

🔌 Steadier connections. The app now recovers from flaky networks without getting stuck.

No action needed on your side.

For your boss

Slack DM · big-picture

AAlex (CEO)· DM
C

changelog-bot APP

Shipped this week: closed the urgent login-security issue 3 customers reported, and released dark mode — our #1 request (214 votes).

Also killed the bug that duplicated background jobs after each deploy.

Zero downtime.

↑ Same 6 commits, same 2 tickets — three finished release notes. You wrote zero words.

👋

From the maker

“I built changelogfa.st because I was tired of writing the same release three times after every ship. Connect your repo, and it's the last release note you'll ever write by hand.”

The maker of changelogfa.st

Pricing

Pay per release. Never per seat.

1 credit = 1 release note. Invite your whole team for free. Try it 1 day, cancel anytime.

Dev

$9 / month

1 dev, ~1 release a day

30 release notes / month

Enough for a release note every day of the month, on 1 repo.

  • Every audience & channel
  • All 8 integrations
  • Your own public changelog page
Generate my release notes
Most popular

Pro

$29 / month

1 team, 120 releases a month

120 release notes / month

≈ 4 a day — daily notes across a handful of repos, with room to spare.

  • Every audience & channel
  • All 8 integrations
  • Your own public changelog page
Generate my release notes

Growth

$79 / month

Many repos, 500 releases a month

500 release notes / month

≈ 16 a day — for many repos shipping non-stop.

  • Every audience & channel
  • All 8 integrations
  • Your own public changelog page
Generate my release notes

Ship the code.
We'll ship the announcement.

Connect your repo, pick a trigger, and your team and your users hear about it 60 seconds after you merge. You write zero words.