DEV Community: Kavin Jey

Your changelog page has no readers — here's what actually works

Kavin Jey — Wed, 08 Jul 2026 11:21:54 +0000

Most indie SaaS founders I know have the same changelog problem: they ship every week to GitHub, nobody writes release notes, and if there IS a changelog page it has not been updated in months.

The result? Users do not know what changed. They churn thinking the product is stagnant. They email support about features that shipped three months ago.

The usual advice is "just write a changelog" -- but that ignores why founders skip it: it takes real time, interrupts the shipping flow, and the right format is never obvious.

What actually works: your merged PRs are already a changelog

Your pull requests are a changelog -- just not formatted for users. The pattern that works:

Pull your recent merged PRs (the titles are 80% of the work)
Reframe from technical to user-facing ("fix null pointer in auth" becomes "fixed a login error some users saw after signup")
Group by theme: Features, Fixes, Improvements

I built a free tool that does step 1 in about 20 seconds:

tryshiplog.io/tools/github-changelog-generator -- paste any public GitHub repo URL, get your recent merged PRs formatted into release-note structure. No account, no card, no waitlist.

Honest about what it does: it reads merged PRs via the GitHub API and formats them into groups. It does NOT currently rewrite them into polished prose -- you get structured raw material to copy and edit from. Works on any public repo right now.

The paid product (Shiplog, $19/mo pre-launch at tryshiplog.io) connects to private repos and embeds an in-app changelog popup in your product. But the free tool works for any public repo today, no signup needed.

What is your current changelog workflow? GitHub Releases, a dedicated tool, or just... nothing?

The State of Changelog Tools for Indie SaaS in 2026

Kavin Jey — Sun, 05 Jul 2026 03:30:43 +0000

If you're a solo founder or small team shipping on GitHub, at some point someone asked you: "what changed in the last release?"

And if you're honest with yourself, your answer was probably a Notion page nobody reads, a GitHub releases tab your users don't know exists, or "I'll get to it."

A changelog sounds like a low-priority vanity feature. But here's what I've learned building a SaaS: when you ship frequently and users don't know what changed, they churn quietly — not because the product got worse, but because they never noticed it got better.

Why Headway stopped being the answer

For years, Headway was the indie-hacker answer to this problem. Beautiful in-app widget, dead simple setup, priced reasonably. A lot of us put it in our sidebars and called it done.

The problem: Headway hasn't shipped a meaningful update since roughly 2020. No GitHub sync. No AI generation. No email notifications to push updates out to users. The integration ecosystem it was built for has moved on, and the product hasn't.

Search "Headway alternatives changelog" and you'll find threads on Indie Hackers and Reddit full of people actively looking for something else. That's not a dead category — it's one where the go-to tool has been abandoned and nobody decent has filled the gap at the indie-hacker price point.

What's actually available in 2026

Here's an honest look at the main options:

Tool	Price	AI generation	GitHub sync	Email digest	In-app widget
Headway	$29/mo	No	No	No	Yes
AnnounceKit	$79-129/mo	Partial	No	Yes	Yes
Beamer	$49-499/mo	No	No	Yes	Yes
Shiplog	$19/mo	Yes	Yes	Yes	Yes

A few things worth noting:

AnnounceKit is well-built and widely used. If you're a funded team or have a larger user base that needs NPS surveys and user segmentation, it earns its price. For a bootstrapped founder, $79/mo for a changelog widget is hard to justify before you're at serious MRR.

Beamer is similarly full-featured and similarly priced for growth-stage SaaS teams. Their entry tier has gotten more reasonable, but the feature floor has shifted up — lots of functionality you won't use when you're a 1-2 person team.

Headway still works as a basic widget, and if you're willing to write everything manually, it does the job. But there's no automation, no email delivery, and it's unclear how much longer the product will be maintained.

The actual problem isn't the changelog page

Here's the insight I kept running into: the bottleneck isn't creating a changelog. It's that publishing is not the same as communicating.

Most indie SaaS founders have a changelog somewhere. A public releases page, a Notion doc, a GitHub releases tab. Users just don't visit it. A changelog page is like a support doc — it's there when people go looking, but it doesn't reach users who don't.

The tools that actually move the needle on retention are the ones that push updates out:

An in-app popup widget catches active users the next time they open the app
An email digest reaches users who haven't logged in recently

Those two things together mean your users actually learn what you shipped.

What I ended up building

After looking at these tools and not finding anything under $49 that had GitHub PR sync + AI generation + widget + email in one package, I built Shiplog to solve this for myself.

The flow: connect your GitHub repo, it reads your merged PRs, and generates customer-friendly release notes — not the technical commit messages, but the "here's what improved for you" version. Those notes get published to a hosted public changelog page, an embeddable in-app widget, and an optional email digest to subscribers.

It's $19/mo. Built specifically for indie SaaS founders and small teams who ship on GitHub and don't have time to write release notes manually.

The pattern worth following regardless of tool

Whatever tool you use, the thing that's actually worth building is the push layer. A static page is table stakes. What actually retains users:

In-app notification on login — users see what changed the next time they open the app. Even a simple badge or banner beats nothing.
Email on significant releases — monthly or on major features, not every minor bug fix. Users who opted into notifications want to hear from you.
User-facing language, not developer language — "Fixed a bug in the export pipeline" means nothing. "CSV exports now work correctly for reports with 1000+ rows" is the same thing, but useful.

The mechanical act of writing a changelog entry isn't the hard part. It's building the habit, and building the delivery layer so users actually see what you shipped.

If you're currently on Headway and frustrated by the stagnation, or paying AnnounceKit prices on a bootstrapped budget, it's worth revisiting what you actually need from a changelog tool in 2026.

Why I Stopped Writing Changelogs (And How I Automated Them Instead)

Kavin Jey — Thu, 25 Jun 2026 01:06:00 +0000

Every week, I ship. New feature here, bug fix there, a small quality-of-life improvement I've been meaning to knock out for months. GitHub gets the commit. My users? They get nothing.

No changelog. No release notes. Not even a vague "we've been busy" tweet.

I'm not lazy — I just never had the time to write them. And I suspect you don't either.

The Changelog Guilt Trip

There's a specific kind of founder guilt that hits when you ship something you're proud of... and then watch users complain about the exact problem you just fixed.

You fixed it three weeks ago. It's been live. But nobody knows.

Or worse: a paying customer churns because they think the product is stagnant. "Seems like they're not really developing it anymore," their offboarding survey says. You just shipped 12 pull requests that month.

This is the changelog problem. And it's not about documentation — it's about communication, trust, and adoption.

Why Release Notes Actually Matter

When users don't know what changed, three bad things happen consistently:

Support burden goes up. Users file tickets for bugs you've already fixed. You spend 20 minutes explaining that yes, this was patched — in a release you never announced anywhere.

Feature adoption stays low. You built something useful. Users never discovered it because the only announcement was buried in a GitHub commit message titled "feat: add CSV export."

Perceived stagnation kills retention. Monthly active users watch their dashboard and draw the wrong conclusion: "Nothing is changing here." The product feels dead even when it isn't.

Headway figured this out early and made it stupidly easy to post a changelog to an embeddable widget. Thousands of indie SaaS products still run on it. The catch: Headway stopped shipping meaningful updates around 2020. No email notifications. No GitHub sync. No AI generation. The alternatives that exist — AnnounceKit, Beamer — start at $50-130/month, which is a lot to spend before you've hit $500 MRR.

What I Tried First

I tried a few things before admitting the real problem:

Notion doc — Lasted two releases. Then I forgot about it entirely.
Twitter threads — Great reach, terrible format. Nobody reads a 12-tweet thread about a minor API change.
GitHub Releases — Technically correct. Zero non-technical users ever clicked that tab.
Writing changelogs manually — Took 45 minutes per release. I'd abandon it after every second sprint when time ran short.

The issue isn't willpower or good intentions. It's friction. Writing customer-friendly release notes requires translating developer language into human language, and that context-switching is expensive when you're a one-person SaaS.

How AI Changes the Equation

Here's the thing: pull requests already contain most of what you need.

The PR title, description, and linked issues all carry context about what changed and why. A PR titled "fix: users getting logged out on mobile when session expires" tells you everything you need to write a user-facing changelog entry. You just never have time to actually write it.

What if the AI wrote it for you?

That's the core idea behind Shiplog. Connect your GitHub repo and it watches for merged PRs. When you ship, it reads those PRs, generates customer-friendly release notes — focused on user impact, not implementation details — and publishes the update to:

A hosted public changelog page with a shareable link
An embeddable in-app popup widget (one <script> tag, drops into any app)
Optional email digests to subscribers who opt in

No writing. No formatting decisions. No remembering to post. It just runs.

The AI is smart enough to know that "refactor: extract auth middleware to utils" shouldn't surface to users, but "fix: users getting logged out on mobile" absolutely should. It filters, rewrites for clarity, and groups related changes. The output reads like a founder who actually communicates — not a raw commit log.

What This Actually Changes

No more dreading the end of every sprint. No more "oh god, I need to write the changelog" moment.

Your users know what shipped. New features get discovered because they're announced — not buried in a GitHub tab nobody checks. Support tickets for already-fixed bugs drop. And customers start mentioning the changelog when they upgrade, saying it makes the product feel "alive and actively maintained."

That last part surprised me most. I underestimated how much perceived momentum matters for retention. You can be shipping constantly and still lose customers who think you've abandoned the product — because they never see the signal that you haven't.

The changelog is that signal.

Try It Yourself

If you're a founder shipping weekly but skipping release notes, the friction is the real problem. Not your priorities, not your discipline.

Try the live demo at Shiplog — paste any public GitHub repo URL and it generates a sample changelog in under 30 seconds. No signup required. See exactly what your users would get.

I built this because I needed it. If you're in the same boat, I'd love to hear how it goes.