create-draft-release-notes

Provide a release tag like v2.0.6 and the target repository. The workflow uses the gh CLI to generate notes from the previous tag, then runs a Node.js script that groups items by conventional commit type and saves the organized body back to the draft.

Items are classified by their conventional commit prefix: feat maps to New Features, fix to Bug Fixes, perf to Performance, refactor to Refactor, docs to Document, and types with an exclamation mark to Breaking Changes. Everything else falls under Other Changes.

The workflow falls back to generating notes through the GitHub API when read access exists, then returns the organized Markdown in the conversation with manual steps to create the draft at the repository's releases page.

Yes, when the repository uses npm staged publishing, it inspects the latest merged release PR for changed package.json files and verifies each public package version is live on npm. If any are missing, it stops and lists the packages awaiting approval.

Yes, run the script directly with a Markdown file path or pipe content via stdin. It reorganizes the What's Changed section into categorized sections while preserving all original item text, authors, and links.