Launch templateProduct and listing copy
Changelog entry template
A public changelog shows buyers and search engines that the product is alive, and it gives every release a page you can link. Write entries for users: what they can do now, not which files changed. Group changes so people can scan for what affects them.
Use it for
- Every release, however small.
- The launch itself (v1.0 is a changelog entry).
- Store "What's New" fields, trimmed down.
Limits and rules
- App Store "What's New" text can be up to 4,000 characters and is required for every version after the first.[1]
The template
Copy it, then replace everything in [BRACKETS]. Delete lines that don't apply rather than leaving them vague.
## [VERSION] - [YYYY-MM-DD] [ONE-SENTENCE SUMMARY OF THE MOST IMPORTANT CHANGE] ### Added - [NEW CAPABILITY, IN USER TERMS] ([LINK TO DOCS]) ### Changed - [WHAT BEHAVES DIFFERENTLY AND WHY] ### Fixed - [BUG USERS SAW, DESCRIBED AS THEY SAW IT] ### Removed - [WHAT'S GONE AND WHAT TO USE INSTEAD] Thanks to [USERS WHO REPORTED OR REQUESTED, WITH PERMISSION].
How to fill it in
[VERSION] - [DATE]
ISO date so it sorts; semantic version if you use one.
[SUMMARY]
The one change most users care about.
Removed
Always say what to use instead.
Filled example
Fictional example. Paperlark is a fictional product we made up for these examples: an invoice-reminder tool for freelancers that sends polite follow-ups when a client pays late. Names, prices and details are invented to show the template filled in; they aren't a real company or real results.
## 1.4.0 - 2026-09-23 You can now pick a "final notice" tone for invoices more than 30 days overdue. ### Added - Final notice tone for invoices 30+ days overdue (docs: paperlark.example/docs/tones) - CSV export of all reminders sent ### Changed - Reminders now send at 9 a.m. in your client's time zone instead of yours ### Fixed - Invoices with a comma in the amount (e.g. 1,200.00) now parse correctly ### Removed - The weekly summary email; the same info is on your dashboard Thanks to Dana and Luis for reporting the comma bug. (Fictional example.)
Do
- Date every entry.
- Write in user terms.
- Link to docs for new features.
- Give each release its own URL.
Don't
- Don't paste commit messages.
- Don't hide breaking changes.
- Don't skip small releases; they show momentum.
FAQ
Does a public changelog help SEO?
It gives each release an indexable page and shows the product is maintained. Link new features to their docs.
How should I group changelog entries?
Added, Changed, Fixed and Removed is a widely used format that lets readers scan for what affects them.
Changelog or release notes?
A changelog is the running log; release notes are the fuller story for a notable release. Many teams use both.
Launch guides that use this template
Sources
Checked . Platforms change their rules; open the source before you rely on a number.
Related templates
- Release notesRelease notes for a notable launch or version: what's new, why it matters, how to use it, upgrade steps and known issues, with a filled example.
- Post-launch retroA post-launch retrospective: goals vs results, channel by channel, what worked, what didn't, surprises and next steps, with a filled example.
- App store descriptionFill-in App Store and Google Play listing copy within each store's limits: name, subtitle, promo text, short and full description, keywords.