For CTOs, CPOs & engineering leads
Know what your team shipped.
Every Monday, an executive summary of last week's releases lands in your inbox — built from your team's commits and Linear or Jira tickets, written in outcomes, not file names. Your team changes nothing.
Connect GitHub in 2 minutes · plans from $9/month · cancel anytime
Your inbox
changelogfa.st
to me
Mon 9:00
What shipped — week of Aug 4
3 releases across 2 repos. The highlight: customers can now pay by invoice.
Invoice payments are live
Customers on annual plans can now request an invoice at checkout instead of paying by card — the most-asked billing request this quarter.
Onboarding is one step shorter
New users land in a ready-to-use workspace; the sample-data step runs in the background.
Fixed: exports over 10k rows
Large CSV exports no longer time out. 14 support tickets closed.
6 releases were internal-only (dependencies, tooling) and were filtered out.
Example — written and sent automatically
Sound familiar?
Your team ships every day. Your picture of it updates at the next meeting.
The information exists — it's spread across merged pull requests, closed tickets and release tags that nobody outside the repo reads. Asking means interrupting; not asking means finding out in the retro.
What Monday looks like
One email. Outcomes only.
An example of the digest — each point is traced back to the real pull requests and tickets behind it. Dependency bumps and internal tooling are filtered out, not summarized.
What your team ships
11 merged PRs · 2 repos · last 7 days
feat: [PROJ-214] invoice payment at checkout
feat: async sample-data step in onboarding
fix: csv export timeout on large datasets
chore: bump dependenciesnoise · filtered
chore: refactor build scriptsnoise · filtered
2 linked tickets
PROJ-214Annual customers can't pay by invoice
PROJ-198Exports over 10k rows time out
What you receive
Your inbox
changelogfa.st
to me
Mon 9:00
What shipped — week of Aug 4
3 releases across 2 repos. The highlight: customers can now pay by invoice.
Invoice payments are live
Customers on annual plans can now request an invoice at checkout instead of paying by card — the most-asked billing request this quarter.
Onboarding is one step shorter
New users land in a ready-to-use workspace; the sample-data step runs in the background.
Fixed: exports over 10k rows
Large CSV exports no longer time out. 14 support tickets closed.
6 releases were internal-only (dependencies, tooling) and were filtered out.
Why this exists
A CTO asked for it first.
changelogfa.st started as per-release notes for fast-shipping teams. Then a CTO asked in a community Slack for “a summary of what shipped, every week”. Same problem, one level up: not “is this feature done?” but “what did we ship at all?”. The weekly digest is now the feature users mention most.
How it works
- 1Connect GitHub (or GitLab / Gitea) — and Linear or Jira if you use them.
- 2Every Monday, the week's merges and closed tickets become one executive summary — written from the intent in the tickets, not the diff.
- 3It lands in your inbox — and in Slack for the team, on a public page for customers, if you want the same week told to every audience.
Your developers install nothing and change nothing — no commit conventions, no extra fields, no process.
Next Monday, know.
Two minutes to connect a repo. Your first digest covers this week.
Plans from $9/month · no free tier, no surprises