Product Changelog

Rewrite raw developer release notes into a polished, user-friendly product changelog. Release version: [version number or date] Raw dev notes: [paste your internal notes, commit messages, or Jira tickets here] Target audience: [end users / technical customers / both] Product name: [name of the product or feature area] Rewrite the changelog following these rules: 1. Lead with user benefit, not technical implementation ('You can now export to PDF' not 'Added PDF serializer') 2. Group changes under: New Features, Improvements, Bug Fixes, and (if applicable) Deprecations 3. Write each item as one sentence in active voice, max 25 words 4. For new features: add a one-sentence 'Why this matters' in italics 5. Remove internal jargon, ticket numbers, and engineer names 6. Highlight the top 1–2 changes with a brief paragraph at the top ('What's new in [version]') 7. End with a 'How to update' one-liner if applicable Tone: clear, friendly, confident. Write for the user who doesn't follow your GitHub commits.