Ship a changelog without writing one.

For small teams who merge PRs faster than they write about them. Connect your GitHub repo and ChangelogPilot drafts customer-ready release notes from your merged PRs. You approve, it publishes.

Join the beta

From merged PR to published entry.

Merge a PR and we draft a changelog entry in plain English — written the way you'd explain it to a customer, not the way a commit message reads. Review it in seconds, not minutes.

No blank page, ever.

Most changelogs stay empty because writing is the bottleneck, not intent. We remove the writing. You bring the judgment. What's left is a quick review, not a writing task.

A changelog your users can actually read.

Publish to a hosted public page — no deploy step, no embed config. A clean URL you can link from your app or docs and forget about until the next merge.

What your customers actually see

The entries below are real output from a real repository, drafted by ChangelogPilot the same way yours would be. This is what gets published.

June 6, 2026 at 9:08 AM UTC

New Features

  • The landing page now displays new, benefit-focused copy with the headline "Ship a changelog without writing one." — emphasizing what users can accomplish without technical jargon.
  • Call-to-action button labels throughout the site have changed from "Get early access" to "Join the beta" to better reflect the current stage of the product.
  • The changelog generation system is now more robust and secure, using Anthropic's forced tool use to eliminate the risk of unparseable responses from the language model being inserted into the changelog.
  • The changelog entry prompt now explicitly enforces bullet-point format, ensuring generated entries are concise, benefit-focused statements rather than prose paragraphs.

Improvements

  • The landing page now follows the standard Tailwind UI marketing design system, with improved typography scale, spacing, and visual hierarchy.
  • Repository and connection forms in settings now use consistent card styling throughout the settings pages, improving visual hierarchy and alignment with the product design system.
  • Login and onboarding pages now follow a consistent, modern design pattern with clearer visual hierarchy and improved focus on primary actions.
  • The login and onboarding forms are now visually contained in a card layout, making the interface clearer and easier to navigate.
  • Error messages are now clearer and more helpful, replacing generic prompts with specific explanations of what went wrong and what to do next.
  • GitHub account connection errors now use plain language to explain the issue instead of technical terminology, making it easier to understand what action is needed.
  • The public changelog page now uses refined typography and spacing, with improved readability for long-form content and a cleaner visual hierarchy.
  • The landing page hero now uses a clean, modern system font stack and centered layout with a teal call-to-action button, bringing the marketing surface into line with brand guidelines.

Bug Fixes

  • Signup errors from the email service now display a friendly message on the landing page instead of a raw error response, making it clear what went wrong without exposing technical details.
  • When signup fails, your email is pre-filled in the form so you can quickly try again without retyping it.
  • LLM responses that include markdown code fences or trailing text after the JSON no longer cause parsing errors.