Ship it, then say it well.
Guides to changelogs, release announcements, docs and developer relations, for teams that build developer tools.
How to Write a Changelog Developers Actually Read (With Examples)
What goes in a changelog, how to group and order entries, how to word breaking changes, fixes and performance wins, what to leave out, and a template you can copy.
Read the guide
How to Announce a Product Release on X: 10 Post Formats for Developer Tools
Ten X post formats for release announcements, matched to the kind of change (launch, feature, fix, performance, breaking), with templates, examples and the rules that apply to all of them.
Release Notes vs. Changelog: What's the Difference and Do You Need Both?
A changelog is a cumulative technical record; release notes explain one release to users. Who each is for, what goes in them, where GitHub Releases fits, and how to write both without doing it twice.
How to Automate Your Changelog From GitHub: Conventional Commits, SemVer and Release Tools
How changelog automation works, and how to set up GitHub's generated release notes, release-please, semantic-release, Changesets and git-cliff, with a comparison and what none of them do.
Docs Drift: How to Keep Documentation in Sync With Your Code
Why documentation drifts from code, how to find the drift you already have, and the practices that stop it: docs next to code, tested examples, generated reference, docs checks in CI and a release step.
Developer Relations for Startups: How to Do DevRel Without a DevRel Hire
What developer relations means at a startup, the ship-announce-document-listen loop, a two-hour weekly cadence, what to skip, and when to hire a developer advocate.
Let the next release write its own changelog.
DevRelay drafts the changelog entry, the posts and the docs update when you ship. You approve what goes out.
No credit card · Nothing posts without your approval