release-notes

name	release-notes
description	Generate Quasar-style release notes for a monorepo package (covering every commit since its last released tag), then — on a single confirmation — bump its version, commit and draft the GitHub release. Use when asked to write/draft release notes or a changelog for app-vite, ui/quasar, cli, vite-plugin, icongenie, extras, create-quasar or a utils package.
argument-hint	<package>

Generate release notes for the requested package (a directory or npm name) in the house style, determine the next version from their content, and output them. THEN ask one yes/no "continue?" — on yes, the version-bump commit AND the draft GitHub release follow with no further questions; without it nothing is changed, committed or created.

All remote state comes from the GitHub API (gh) — NEVER git fetch or any other remote git operation. NEVER publish a release, create a tag or push.

1. Preflight

• Freshness gate: the live dev HEAD (gh api repos/quasarframework/quasar/commits/dev --jq .sha) must exist locally (git cat-file -e <sha>); otherwise STOP and tell the user to update their clone.
• Note whether the worktree is clean (git status --porcelain) — a dirty one doesn't block the notes, but blocks step 8's commit; mention it early.

2. Resolve the package

dir	npm name	tag prefix
ui	quasar	quasar-v
app-vite	@quasar/app-vite