The Short Template
# Product Name - Release Name Published: Month Day, Year One short paragraph explaining what changed and who benefits. ## Added - New things customers can use. ## Changed - Improvements to existing workflows. ## Fixed - Bugs, broken links, errors, and reliability issues. ## Removed - Deprecated or retired product surface. ## Security - Permission, privacy, or authentication changes. ## Upgrade Note Say whether customers need to do anything. ## Email Subject Product update: the useful thing is now live
What To Include
Added
New capabilities customers can use.
Added public roadmap embeds for product pages.
Changed
Improvements to existing workflows.
Changed roadmap filters so shipped work is easier to find.
Fixed
Bugs, broken links, reliability issues, and confusing states.
Fixed duplicate invite emails for new teammates.
Removed
Deprecated screens, retired settings, or removed behavior.
Removed the legacy changelog import screen.
Security
Permission, privacy, auth, token, or infrastructure changes.
Patched permission checks for private roadmap updates.
Turn One Update Into Three Assets
The changelog is the structured record. Release notes are the more human explanation. A product update email brings users back to the product. The same shipped changes should feed all three.