Write Release Notes That Inform and Delight

A list of commit messages tells users nothing. This converts your raw changelog into release notes with a headline, a What's New section framed as benefits not feature names, a Fixed section written from the user's frustration, and known issues if you have them. Paste the changelog, get notes that read like a human wrote them.

Write release notes for version {VERSION_NUMBER} of {PRODUCT_NAME}. The changelog entries are: {RAW_CHANGELOG}.

Transform the raw changelog into polished release notes structured as: a one-sentence release headline, a 'What's new' section (user benefits, not feature names), a 'Fixed' section (frame bugs from the user's frustration, not the engineer's fix), and a 'Known issues' section if any exist in {KNOWN_ISSUES}.

Write in an active, warm tone appropriate for a {PRODUCT_TONE} product. Each bullet must start with a verb. Strip out internal ticket numbers and implementation details. Keep the entire document under 300 words. Include a migration note if any breaking changes are present in the changelog.