Turn this changelog into release notes customers will actually read.
Raw changes shipped:
{{paste your changelog / list of what shipped — features, fixes, improvements}}
Format:
- **Headline** (1 line — what's the most exciting thing in this release, in customer terms not engineer terms)
- **What's new** (2-4 actual features, lead with the one a user would notice first)
- **Improvements** (1-3 things that make existing workflows better — be specific about what got faster/cleaner)
- **Bug fixes** (1-line list, only customer-visible ones)
- **Coming next** (optional, only if there's a real teaser)
For each item: write it in terms of what the user can now do, not what we built. "You can now export to CSV" not "Added export functionality."
Skip:
- Internal infra changes
- Refactors customers wouldn't notice
- Bugs that 3 users hit (unless they were severe)
If this release is mostly housekeeping, tell me and suggest skipping public release notes.release notesproductchangelog