What problem does it solve?
Writing consistent, well-formatted GitHub release notes from raw commit and PR data is tedious and error-prone, especially when enforcing strict formatting rules around highlights, breaking changes, and changelog links.
Core Features & Use Cases
- Structured Release Notes: Produces release notes in the established Medusa style with strict section ordering (Highlights, Features, Bugs, Documentation, Chores, Other Changes, New Contributors, Full Changelog).
- Release Type Classification: Distinguishes minimal patch releases, single-highlight releases, multi-highlight releases, and releases with breaking changes based on changesets and PR labels.
- Breaking Change Handling: Embeds breaking changes inside Highlight subsections with a 🚧 marker, migration code blocks, and nuance blockquotes instead of a separate top-level section.
- Use Case: Given a list of commits and PR metadata for a new Medusa version, generate a complete draft release description with correctly formatted bullets, author links, PR links, and the mandatory Full Changelog compare link.
Quick Start
Ask the assistant to write release notes for the new Medusa version using the provided list of commits and PR metadata.