GitHub changelog generator

Your GitHub history is not the same as your customer story.

ChangeCrab helps teams turn merged PRs, issues, and release notes into a public changelog customers can understand, subscribe to, and trust.

Create your changelog Start Premium trial

Free plan available. Upgrade when you need AI, API, scheduling, and more changelogs.

PRs Issues Customer changelog

PRs Start from the GitHub work your team already tracks

Themes Group technical changes into customer-readable updates

Page Give every release a durable public home

GitHub to changelog

Merged pull requests

#218 add SSO domain hint #221 fix invite token expiration #225 improve onboarding checklist #230 refactor billing retry service

GitHub Labels Authors

Customer update selection

New SSO setup guidance, more reliable team invites, and a clearer onboarding checklist are worth announcing. Internal billing refactor stays out of the customer post.

Signal Impact Editing

ChangeCrab post

Team setup is smoother this week: admins get clearer SSO guidance, invites stay valid for the expected window, and new workspaces can finish onboarding faster.

Public URL RSS Widget

New update ready for customers Published to public page, widget, RSS, and subscriber channels.

Follow-up context stays attached Links, categories, and customer impact live with the update instead of drifting across tools.

The problem

GitHub-generated release notes are useful. They are not enough.

PR titles are written for maintainers

They often miss customer benefit, migration notes, and rollout context.

Internal work creates noise

Refactors, tests, dependency bumps, and infrastructure changes can bury what users need.

GitHub is not your product update hub

Most customers will not subscribe to GitHub releases, but they will read clear updates in your product or docs.

Workflow

The GitHub release workflow for customers

Source

Collect the release source

Use GitHub Releases, PR labels, issues, or your own release checklist.

Shape

Separate internal work from customer updates

Keep what matters to users, explain it in plain language, and include links where useful.

Publish

Publish and distribute

Use ChangeCrab as the public changelog, then share through widgets, email, RSS, and API workflows.

Implementation

From GitHub release data to a published update

Start with GitHub release data, decide what customers need to know, then publish the finished update through ChangeCrab.

Create your changelog

gh pr list \
  --state merged \
  --search "merged:2026-06-01..2026-06-22" \
  --json number,title,labels,author

Group these merged PRs into release notes for customers.
Exclude internal refactors unless they affect users.
Call out any migration, permission, or billing impact.

curl -X POST https://changecrab.com/api/changelogs/your-id/posts \
  -H "X-API-Key: $CHANGECRAB_API_KEY" \
  -H "Content-Type: application/json" \
  -d @customer-release-note.json

What you get

Built around the parts of product communication teams use every week.

Customer-facing changelog pages

AI drafting for Premium and trial workflows

Categories for New, Improved, Fixed, and Breaking updates

RSS and subscriber delivery

API and MCP publishing paths

Widgets and badges for docs, apps, and READMEs

GitHub fit

The useful work is curation, not copying the PR list.

GitHub contains the source material. The changelog page should explain what customers can actually use.

Start with merged work

PRs, labels, issues, and release checklists help identify what changed.

Separate internal noise

Refactors, tests, and dependency bumps should stay out unless they change customer experience.

Link technical depth when needed

Customer-facing entries can still point to GitHub releases, PRs, or migration docs for readers who need detail.

Buyer questions

Questions teams ask before choosing a changelog workflow.

Why not just use GitHub Releases?

Use GitHub Releases for developer artifacts. Use ChangeCrab when customers, prospects, support, and product marketing need a cleaner update history.

Can we keep technical details?

Yes. Link to the technical release, migration guide, or pull request from a customer-friendly summary.

Does this require a GitHub integration?

No. You can start by pasting release context, then use API, MCP, or automation as the workflow matures.

Turn GitHub activity into product momentum.

Create a ChangeCrab changelog and give customers the version of your release they can use.

Create your changelog View example changelog