The technical truth
OAuth now uses PKCE to block authorization-code interception. The worker heartbeat race is gone — state transitions sit behind a mutex. WebSocket reconnect backs off exponentially with jitter.
Reads GitHub, GitLab, Gitea, Linear & Jira
Release notes thatwrite themselves.
You merge the PR. 60 seconds later your changelog is in Slack, in your users' inbox, and on your public page — in three different voices.
You save 2 hours every release.
Connect a repo in 30 seconds · 1-day trial · cancel anytime
Live demo — v2.4.0
Your commits go in
feat: [PROJ-132] OAuth flow with PKCE
fix: worker heartbeat race condition
docs: migration notes
feat: websocket reconnect logic
feat: [PROJ-128] dark mode toggle
chore: bump dependencies
A real release note comes out
Output: customer-ready update
Channel target: cto@company.com
Inbox1 of 247
v2.8.0 shipped — OAuth security & realtime stability
InboxC9:42 AM
changelog-bot <notify@changelogfa.st>
to me, product-team
Hey team,
We just shipped v2.8.0. Highlights:
- OAuth flow now uses PKCE
- Worker heartbeat race condition fixed
- WebSocket reconnect more reliable
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.
How it works
1 release in. 3 versions out.
changelogfa.st reads your commits, PRs and tickets, then writes the same release for everyone who needs it. Same input, three voices, zero copy-paste.
The version they actually read
Signing in is safer, even on public Wi-Fi. The app stays connected when your network drops. Background updates no longer get stuck.
The 3-line recap
Shipped a major security upgrade, killed a long-standing reliability bug, and made the mobile app stable on bad networks. Zero downtime.
↑ Same 6 commits. Three different release notes. One workflow run.
Plugs into the 8 tools you already ship with
GitHubGitLabGiteaLinearJiraSlackGmailWebhook
👋
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, 10 releases a month
10 release notes / month
- ✓Every audience & channel
- ✓All 8 integrations
- ✓Your own public changelog page
Pro
$29 / month
1 team, 40 releases a month
40 release notes / month
- ✓Every audience & channel
- ✓All 8 integrations
- ✓Your own public changelog page
Growth
$79 / month
Many repos, 150 releases a month
150 release notes / month
- ✓Every audience & channel
- ✓All 8 integrations
- ✓Your own public changelog page
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.