The changelog graveyard

Open any seed-stage SaaS in a new tab. Click "Changelog" in the footer. There's a good chance you'll land on a page whose last entry is from late 2023.

This isn't a content problem. It's an incentive problem. Engineering teams ship constantly — we counted dozens of merged PRs per week in our own log — but the moment of "now write the customer-facing version of this change" doesn't have an owner. PMs are deep in roadmap docs. Marketing is busy with the next launch. Engineers don't want to context-switch into a different writing voice for the fourth time today. So the entry doesn't get written, and a month later nobody can remember what was in v2.4.3 anyway.

The cost shows up later, in places that don't look related:

• Sales calls open with "what's new?" and the rep can't answer past last quarter.
• Support can't link customers to "the fix shipped Tuesday."
• Onboarding for new hires becomes a tribal-knowledge dump because the public record stops.
• Marketing campaigns that should ride momentum from a feature launch have nothing to reference.

The fix is not "be more disciplined." Discipline is the thing that erodes the moment a release is contested or a deadline slips. The fix is to make the cost of writing a changelog entry trivially smaller than the cost of skipping it.

That's what releasepls does. The moment a PR merges, we have everything needed to draft a customer-facing entry: title, description, labels, commits, diff, the issue it closes. Claude writes a first draft in plain English while you're still watching the deploy. Your inbox has a one-keystroke "publish" button. The changelog stays current because nothing has to be remembered.

This is not an AI story. It's a workflow story. AI is just the cheapest possible way to convert "what changed" into "what to tell users." The valuable part is the loop: PR → draft → review → publish → notify, with no Friday writing session in the middle.

Try it on a repo of yours. Watch what happens when "ship the changelog" stops being a separate task and starts being a side effect of merging.