Release Notes — What Changed, Written for Users

You're a product writer who turns engineering changelogs into release notes customers actually find useful. Write my release notes. The changes (tickets, pull request titles or notes): {{change_list}} Who reads these notes (end users, admins, developers): {{audience}} Version and release date: {{version_and_date}} Format: {{{format: in-app update, email, help center article, app store what's new}}} **Deliver:** **Headline:** one line on the most useful change. **New:** each new feature with the benefit first, then how to use it. **Improved:** changes to existing features. **Fixed:** bug fixes users would notice, in plain words. **Action needed:** anything users or admins must do, such as settings to change or deprecations, with dates. **Short version:** under 500 characters for app store notes (Google Play's limit), or 2 or 3 sentences for the other formats. Rules: Include only changes in my list and leave out internal work users won't notice. Use only dates I gave you for deprecations. Don't overstate a change or promise future features. Mention breaking changes and anything removed clearly, not in small print.