Generate Product Changelog Entry

You are a product communications specialist writing changelog entries. Create clear, engaging updates that inform users about changes.

**Changes to Document:**
{{changes}}

**Version/Release:**
{{version}}

**Release Date:**
{{release_date}}

**Audience:**
{{audience}}

Write a changelog entry:

---

## [Version Number] — [Release Date]

### [Release Title/Theme] (optional)
[One sentence summary of the release theme if applicable]

---

### ✨ New Features

**[Feature Name]**
[1-2 sentence description of what it does and why users will care]

- [Specific capability]
- [Specific capability]

[Screenshot/GIF placeholder: Describe what to show]

**[Feature Name]**
[Same structure...]

---

### 🔧 Improvements

- **[Area]**: [What improved and the user benefit]
- **[Area]**: [What improved and the user benefit]
- **[Area]**: [What improved and the user benefit]

---

### 🐛 Bug Fixes

- Fixed an issue where [specific problem users experienced]
- Resolved [specific problem] that affected [who/when]
- [Problem] no longer occurs when [trigger condition]

---

### ⚠️ Breaking Changes (if any)

**[Change]**
- **What changed:** [Technical details]
- **Who is affected:** [Specific users/use cases]
- **Migration path:** [What users need to do]
- **Deadline:** [When old behavior stops working]

---

### 📚 Documentation

- [New/updated docs if relevant]

---

### Coming Soon

[Optional: Tease next release if appropriate]

---

**Questions?** [Support link/contact]

---

## Writing Notes

**Tone considerations:**
- [Platform-appropriate voice]

**Distribution:**
- Changelog page: Full version
- Email: [Abbreviated version focusing on highlights]
- In-app: [One-liner for notification]
- Social: [Tweet-length highlight]

Lead with user benefits, not technical implementation. Be specific about what changed—vague changelogs frustrate users.