Release notes generator

Release notes generator for teams that ship every week

Turn merged pull requests into clear, customer-facing release notes. Changelog Generator reads what changed, drafts the update, and gives you a polished changelog entry to review before publishing.

Drafts from merged PRs
Customer-ready wording
Hosted public changelog
PostHog

PostHog

Changelog for posthog/posthog

GitHub
April 30, 2026

Enhanced Features & User Experience

New Features

  • Property-Level Access Control: You can now hide sensitive event and person properties from other users in your PostHog project, ensuring that sensitive information like PII is protected.
  • Survey MCP Creation Fields: Survey creation is now more streamlined through MCP, allowing you to set display conditions, schedule, and more in one go.
  • Session Replay Cancellation: Users can now cancel in-flight session summaries, giving you more control over ongoing processes.

Improvements

  • Heatmaps Display: The issue where 'SCRIPT_PLACEHOLDER' showed on heatmaps has been resolved, providing a cleaner, more professional view.
  • Survey Targeting Conditions: AI survey targeting conditions are now generated more reliably across projects.

Why it matters

Release notes slip because the work is already done.

By the time a release is ready, the context is scattered across pull requests, tickets, and team chats. A release notes generator turns that history into a readable update while it is still fresh.

Technical notes need translation

PR titles explain what changed in the code. Customers need to know what they can do now.

Blank pages slow launches

The hardest part is usually starting. A strong draft gives product and marketing teams something to refine.

Updates need a home

Published release notes should be easy to share, index, and revisit long after the launch email is gone.

Workflow

From GitHub history to publishable release notes.

Connect a repository, let the AI summarize the shipped work, then edit the draft before it goes live.

Step 1

Connect your repository

Changelog Generator looks at merged pull request titles and descriptions so the draft starts from real shipping activity.

Step 2

Generate the release notes

The AI groups related changes, removes internal noise, and frames each update around user value.

Step 3

Review and publish

Edit the draft, keep the wording on-brand, and publish it to a public changelog page.

Example release note

Technical shipping history, rewritten for customers.

Input from your shipped work

  • PR #1842: Add saved filters to reports
  • PR #1849: Fix CSV export timeout for larger workspaces
  • PR #1851: Improve empty state for first-time admins

Generated draft

Better reporting workflows for busy teams

Reports are easier to return to, export, and set up for new admins. Saved filters keep frequent views close at hand, larger CSV exports are more reliable, and first-time setup now gives clearer next steps.

  • Save frequently used report filters and reopen them later.
  • Export larger datasets with fewer timeout errors.
  • Guide new admins with a clearer first-report experience.

Use cases

Built for the teams responsible for the announcement.

A release notes generator is useful when engineering has the facts, but product and marketing own the message.

Founders

Keep users aware of weekly product progress without spending Friday afternoon in a doc.

Product marketers

Turn raw shipped work into benefit-led copy that can feed changelogs, emails, and launch notes.

Product managers

Give customers and internal teams a reliable summary of what changed and why it matters.

FAQ

Common questions.

What is a release notes generator?
A release notes generator turns shipped product changes into a readable update. Changelog Generator uses merged GitHub pull requests as the source material, then drafts customer-facing release notes you can edit before publishing.
Can I edit the generated release notes?
Yes. The generated copy is a draft. You can rewrite the headline, adjust sections, remove items, and publish only when the update is ready.
Is this different from a changelog?
Release notes usually explain a release in customer-facing language. A changelog is the ongoing public record of those updates. Changelog Generator helps with both the writing and the hosted changelog page.
Does it work for small weekly releases?
Yes. It is especially useful for teams that ship small improvements often and want a consistent way to explain them.

Related resources

Explore the release notes keyword cluster.

Start now

Turn the next release into a page customers can read.

Connect GitHub, generate the draft, edit the copy, and publish your public changelog from one place.

Generate release notes