ChangelogPilot blog

Notes from building ChangelogPilot — product updates, and how small teams can ship changelogs their customers actually read. Follow along by RSS or Atom.

  1. How often should you publish a changelog?

    Per-release, weekly, monthly or batched. How to pick a changelog cadence that matches your ship rate and doesn't decay into a dusty quarterly page.

  2. How to host your changelog on your own domain

    Why a customer-facing changelog belongs on your own domain, subdomain versus subdirectory, and the practical hosting options with their tradeoffs.

  3. How to write release notes people actually read

    A practical guide to writing release notes for a shipped version — structure, breaking changes, known issues, and what a good entry looks like.

  4. What are release notes?

    What release notes are, what goes in them (and what doesn't), who actually reads them, and how they differ from a commit message or a changelog.

  5. The Keep a Changelog format, and when to break from it

    What the Keep a Changelog standard gets right, its six categories, and when a customer-facing changelog should diverge from the dev-facing format.

  6. Product updates that bring customers back

    Communicating what you shipped is retention work. A plain note about what's new can re-engage a drifting customer before they quietly churn.

  7. How to automate your changelog from GitHub pull requests

    A practical guide to automating your changelog from GitHub pull requests, covering PR hygiene, filtering, categorisation, and reviewing instead of writing.

  8. Release notes vs changelog vs product updates: what to write where

    What release notes, changelogs, and product updates each are, who reads them, how deep each goes, and which channel each one belongs in.

  9. Changelog examples: a teardown of product changelogs worth copying

    Five product changelogs worth studying — the patterns behind them, and what a small SaaS team can steal: structure, cadence, voice, breaking changes.

  10. ChangelogPilot is live

    ChangelogPilot is live. Connect a GitHub repo, get a drafted changelog entry from your merged PRs, and publish — no writing required.

  11. Why we built ChangelogPilot instead of a better changelog editor

    Most changelog tools help you write faster. ChangelogPilot skips the writing. Here's why we think that's the actual problem worth solving.

  12. How to write a changelog people actually read

    A practical guide to writing changelog entries people actually read — categorising changes, handling breaking changes, and knowing what to leave out.