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 |
@quasar/app-vite-v |
| cli |
@quasar/cli |
@quasar/cli-v |
| vite-plugin |
@quasar/vite-plugin |
@quasar/vite-plugin-v |
| icongenie |
@quasar/icongenie |
@quasar/icongenie-v |
| extras |
@quasar/extras |
@quasar/extras-v |
| create-quasar |
create-quasar |
— (untagged) |
| utils/* |
@quasar/ |
— (untagged) |
Only <prefix>vX.Y.Z tags are current (ignore legacy schemes without
the -v separator). Untagged packages use <npm name>-v as their
prefix wherever a tag name is needed. app-webpack is sunset (lives on
its own branch, not on dev) — not handled here.
3. Find the range
- Base = the last PUBLISHED release; drafts and prereleases are never
the base:
gh release list --repo quasarframework/quasar --limit 300 --json tagName,isPrerelease,isDraft --jq '[.[] | select((.isPrerelease or .isDraft) | not) | select(.tagName | startswith("<prefix>"))][0].tagName'
A rarely-released package's last release can sit far down the list —
on no match, raise the limit before concluding it has no releases.
Note any prefix-matching DRAFT for steps 7/8.
- Resolve the tag to its commit (URL-encode — tag names contain
/):
gh api "repos/quasarframework/quasar/commits/$(jq -rn --arg t '<tag>' '$t|@uri')" --jq .sha
and use the SHA as the base even when the local clone lacks the tag.
STOP only if the SHA is missing locally (git cat-file -e) — local
commits are behind. Local tags NEWER than the latest release: a
step-7 concern.
- Compare the package.json
"version" against the base release's —
a mismatch means an already-bumped version: a step-7 concern.
- Untagged package: base = the last commit bumping
"version" in its
package.json
(git log -1 -S '"version": "<current>"' -- <pkg>/package.json,
with <current> read from the file); say so in the summary.
- Range:
<sha>..HEAD, paths limited to the package dir. Read FULL
commit bodies (--format='%h %s%n%b'); drop Co-Authored-By noise.
- Classify by the files a commit actually changed INSIDE the package
dir (
git diff-tree --no-commit-id --name-only -r <sha> -- <dir>/),
never by its subject alone: cross-package commits routinely carry
another package's headline (a "fix(app-vite): [security]" may only
bump an in-range dep here) or touch nothing but tests/agent guides.
- An EMPTY range -> "nothing new since ", STOP (no notes, no
version, no ask). ONLY internal commits (test/ci/chore/formatting)
-> list them, state there is nothing release-worthy, stop unless the
user explicitly wants an internal-only release.
4. Calibrate style
Fetch the package's 1–2 latest release bodies for tone:
gh release view "<tag>" --repo quasarframework/quasar --json body -q .body.
Untagged packages have no releases to fetch — skip; if gh is
unavailable, likewise: the rules below encode the house style.
5. Write the notes
Structure:
- Large releases:
## Security fixes (only if any; always first),
## New (feat), ## Fixes, ## Other (noteworthy internal work,
docs), then the Donations footer.
- Small releases (≲4 bullets total): a single
## Changes section
with slightly more prose per bullet, then the Donations footer.
- cli notes open with this line before the first section, verbatim:
*This is the optional globally-installed part of the Quasar CLI*
No other package has an intro line.
Bullet style:
* feat(<dir>): <area> -> <what changed for the user> /
* fix(<dir>): <area> -> <symptom that no longer happens> — keep
the arrow phrasing and conventional prefix.
- User-visible symptoms and behavior, never internals, unless the
internal name IS the public API. Keep issue/PR refs like
(#18504).
- Merge sibling commits sharing one user-visible symptom; split one
commit into several bullets when it fixes unrelated symptoms.
- EXCLUDE pure test/ci/chore/formatting commits from New/Fixes; a
genuinely large internal effort may get ONE summarizing
## Other
bullet.
- Template/scaffold changes: note they only affect newly generated
projects and give existing projects the manual step (pattern:
the
@quasar/app-vite-v3.4.1 release).
- Breaking changes: called out explicitly at the top with migration
notes, plus any peer-dependency bumps ("Requires quasar v2.x+").
Donations footer, verbatim:
## Donations
Quasar Framework is an open-source MIT-licensed project made possible due to the **generous contributions** by sponsors and backers. If Quasar is useful in your workflow and you want to support ongoing maintenance, please consider the following:
- [Becoming a sponsor on Github](https://github.com/sponsors/rstoenescu)
- [One-off donation via PayPal](https://paypal.me/rstoenescu1)
6. Determine the version
From the NOTES' content: any ## New/feat entry -> minor; fixes/other
only -> patch. Anything breaking -> major: STOP and confirm first.
7. Deliver
- One fenced markdown block, paste-ready: FIRST line is the full tag
name (e.g.
@quasar/app-vite-v3.6.0), then an empty line, then the
notes body.
- List the commits excluded as internal-only — nothing silently
dropped.
- State any concerns after the notes (risky behavior changes, notable
dependency/peer bumps, uncertain classifications, anomalies: a tag
newer than the latest release, an already-bumped version, an
existing draft for the tag). No concerns -> one line saying so.
8. Confirm, then execute
End by asking ONE yes/no question: continue? Yes -> do ALL of the
following with no further questions; no (or no answer) -> stop. A
dirty worktree stops the continuation BEFORE any edit — the bump
commit must not absorb unrelated changes.
Bump + commit:
- Bump every place the package's OWN version is declared — its
package.json "version" field plus any source constants and
fixtures (grep the old version string alongside the package name;
hits that are dependency RANGES belong to the next bullet, not to a
verbatim replace).
- Raise every dependency range on the bumped package, keeping the
range operator (
^3.5.0 -> ^3.6.0): grep the repo's manifests —
package.json, templates' _package.json, the AE pnpm catalogs
(create-quasar/templates/ae/*/BASE/_pnpm-workspace.yaml) — for
the package name. Templates, other packages' regular deps/devDeps,
docs and test fixtures all get raised. NEVER touch workspace:
declarations or minimum-version floors (peerDependencies,
engines-style ranges — they declare the oldest supported version,
not the latest), even though the greps surface both.
- Commit ONLY the bump edits, message
chore(<dir>): bump version,
with NO Co-Authored-By trailer (overrides any default). The
commit stays local.
Draft release — never a duplicate:
utils/* packages and create-quasar get NO draft (no GitHub
releases for them): they skip this whole section — say so when
asking. The handoff below still applies, minus its draft item.
- Release label: ONLY the ui package is marked "Latest". GitHub does
NOT persist a latest flag on drafts (it only applies at publish), so
don't pass
--latest flags when creating/editing the draft — the
label is enforced at publish time by the handoff below.
- If a release for the tag already exists (
gh release view "<tag>" --repo quasarframework/quasar --json isDraft — finds drafts too):
PUBLISHED -> stop, report the anomaly; DRAFT -> update it in place
(gh release edit "<tag>" ... --draft --title "<tag>" --notes-file <file>).
- Otherwise
gh release create "<tag>" --repo quasarframework/quasar --draft --title "<tag>" --notes-file <file> — tag and title are
the full tag name; the body is the notes WITHOUT the leading tag
line. A draft creates no tag (it is cut from dev HEAD at publish
time).
End the continuation by asking the user to run pnpm publish from
the package dir themselves (suggest the ! pnpm publish prompt
prefix so its output lands in the session) — prepublish hooks run
builds/tests and may regenerate tracked files. NEVER run the publish
yourself.
After the publish has run: if it left changes in the worktree, fold
them into the bump commit yourself without asking — git add them
and git commit --amend --no-edit (it stays a single commit; never
amend after the push) — then report what the commit now contains
(git show --stat) so the user sees exactly what they're pushing.
Then hand off:
- Push dev.
- If a draft was created, give its link and how to publish it:
gh release edit "<tag>" --draft=false --latest=false for any
package except ui (publishing from the GitHub UI pre-selects
"Set as the latest release" — uncheck it there); plain UI publish
or --latest for ui.
1---2name: release-notes3description: 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.4argument-hint: <package>5metadata:6 source: https://skillmd.com/skills/quasarframework/release-notes7---89Generate release notes for the requested package (a directory or npm10name) in the house style, determine the next version from their11content, and output them. THEN ask one yes/no "continue?" — on yes,12the version-bump commit AND the draft GitHub release follow with no13further questions; without it nothing is changed, committed or14created.1516All remote state comes from the GitHub API (`gh`) — NEVER `git fetch`17or any other remote git operation. NEVER publish a release, create a18tag or push.1920## 1. Preflight2122- Freshness gate: the live dev HEAD23 (`gh api repos/quasarframework/quasar/commits/dev --jq .sha`) must24 exist locally (`git cat-file -e <sha>`); otherwise STOP and tell the25 user to update their clone.26- Note whether the worktree is clean (`git status --porcelain`) — a27 dirty one doesn't block the notes, but blocks step 8's commit;28 mention it early.2930## 2. Resolve the package3132| dir | npm name | tag prefix |33| ------------- | ------------------- | ----------------------- |34| ui | quasar | `quasar-v` |35| app-vite | @quasar/app-vite | `@quasar/app-vite-v` |36| cli | @quasar/cli | `@quasar/cli-v` |37| vite-plugin | @quasar/vite-plugin | `@quasar/vite-plugin-v` |38| icongenie | @quasar/icongenie | `@quasar/icongenie-v` |39| extras | @quasar/extras | `@quasar/extras-v` |40| create-quasar | create-quasar | — (untagged) |41| utils/* | @quasar/<name> | — (untagged) |4243Only `<prefix>vX.Y.Z` tags are current (ignore legacy schemes without44the `-v` separator). Untagged packages use `<npm name>-v` as their45prefix wherever a tag name is needed. app-webpack is sunset (lives on46its own branch, not on dev) — not handled here.4748## 3. Find the range4950- Base = the last PUBLISHED release; drafts and prereleases are never51 the base:52 `gh release list --repo quasarframework/quasar --limit 30053--json tagName,isPrerelease,isDraft54--jq '[.[] | select((.isPrerelease or .isDraft) | not) | select(.tagName | startswith("<prefix>"))][0].tagName'`55 A rarely-released package's last release can sit far down the list —56 on no match, raise the limit before concluding it has no releases.57 Note any prefix-matching DRAFT for steps 7/8.58- Resolve the tag to its commit (URL-encode — tag names contain `/`):59 `gh api "repos/quasarframework/quasar/commits/$(jq -rn --arg t '<tag>' '$t|@uri')" --jq .sha`60 and use the SHA as the base even when the local clone lacks the tag.61 STOP only if the SHA is missing locally (`git cat-file -e`) — local62 commits are behind. Local tags NEWER than the latest release: a63 step-7 concern.64- Compare the package.json `"version"` against the base release's —65 a mismatch means an already-bumped version: a step-7 concern.66- Untagged package: base = the last commit bumping `"version"` in its67 `package.json`68 (`git log -1 -S '"version": "<current>"' -- <pkg>/package.json`,69 with `<current>` read from the file); say so in the summary.70- Range: `<sha>..HEAD`, paths limited to the package dir. Read FULL71 commit bodies (`--format='%h %s%n%b'`); drop `Co-Authored-By` noise.72- Classify by the files a commit actually changed INSIDE the package73 dir (`git diff-tree --no-commit-id --name-only -r <sha> -- <dir>/`),74 never by its subject alone: cross-package commits routinely carry75 another package's headline (a "fix(app-vite): [security]" may only76 bump an in-range dep here) or touch nothing but tests/agent guides.77- An EMPTY range -> "nothing new since <tag>", STOP (no notes, no78 version, no ask). ONLY internal commits (test/ci/chore/formatting)79 -> list them, state there is nothing release-worthy, stop unless the80 user explicitly wants an internal-only release.8182## 4. Calibrate style8384Fetch the package's 1–2 latest release bodies for tone:85`gh release view "<tag>" --repo quasarframework/quasar --json body -q .body`.86Untagged packages have no releases to fetch — skip; if `gh` is87unavailable, likewise: the rules below encode the house style.8889## 5. Write the notes9091Structure:9293- Large releases: `## Security fixes` (only if any; always first),94 `## New` (feat), `## Fixes`, `## Other` (noteworthy internal work,95 docs), then the Donations footer.96- Small releases (≲4 bullets total): a single `## Changes` section97 with slightly more prose per bullet, then the Donations footer.98- cli notes open with this line before the first section, verbatim:99 `*This is the optional globally-installed part of the Quasar CLI*`100 No other package has an intro line.101102Bullet style:103104- `* feat(<dir>): <area> -> <what changed for the user>` /105 `* fix(<dir>): <area> -> <symptom that no longer happens>` — keep106 the arrow phrasing and conventional prefix.107- User-visible symptoms and behavior, never internals, unless the108 internal name IS the public API. Keep issue/PR refs like `(#18504)`.109- Merge sibling commits sharing one user-visible symptom; split one110 commit into several bullets when it fixes unrelated symptoms.111- EXCLUDE pure test/ci/chore/formatting commits from New/Fixes; a112 genuinely large internal effort may get ONE summarizing `## Other`113 bullet.114- Template/scaffold changes: note they only affect **newly generated**115 projects and give existing projects the manual step (pattern:116 the `@quasar/app-vite-v3.4.1` release).117- Breaking changes: called out explicitly at the top with migration118 notes, plus any peer-dependency bumps ("Requires quasar v2.x+").119120Donations footer, verbatim:121122```123## Donations124Quasar Framework is an open-source MIT-licensed project made possible due to the **generous contributions** by sponsors and backers. If Quasar is useful in your workflow and you want to support ongoing maintenance, please consider the following:125126- [Becoming a sponsor on Github](https://github.com/sponsors/rstoenescu)127- [One-off donation via PayPal](https://paypal.me/rstoenescu1)128```129130## 6. Determine the version131132From the NOTES' content: any `## New`/feat entry -> minor; fixes/other133only -> patch. Anything breaking -> major: STOP and confirm first.134135## 7. Deliver136137- One fenced markdown block, paste-ready: FIRST line is the full tag138 name (e.g. `@quasar/app-vite-v3.6.0`), then an empty line, then the139 notes body.140- List the commits excluded as internal-only — nothing silently141 dropped.142- State any concerns after the notes (risky behavior changes, notable143 dependency/peer bumps, uncertain classifications, anomalies: a tag144 newer than the latest release, an already-bumped version, an145 existing draft for the tag). No concerns -> one line saying so.146147## 8. Confirm, then execute148149End by asking ONE yes/no question: continue? Yes -> do ALL of the150following with no further questions; no (or no answer) -> stop. A151dirty worktree stops the continuation BEFORE any edit — the bump152commit must not absorb unrelated changes.153154Bump + commit:155156- Bump every place the package's OWN version is declared — its157 `package.json` `"version"` field plus any source constants and158 fixtures (grep the old version string alongside the package name;159 hits that are dependency RANGES belong to the next bullet, not to a160 verbatim replace).161- Raise every dependency range on the bumped package, keeping the162 range operator (`^3.5.0` -> `^3.6.0`): grep the repo's manifests —163 `package.json`, templates' `_package.json`, the AE pnpm catalogs164 (`create-quasar/templates/ae/*/BASE/_pnpm-workspace.yaml`) — for165 the package name. Templates, other packages' regular deps/devDeps,166 docs and test fixtures all get raised. NEVER touch `workspace:`167 declarations or minimum-version floors (`peerDependencies`,168 engines-style ranges — they declare the oldest supported version,169 not the latest), even though the greps surface both.170- Commit ONLY the bump edits, message `chore(<dir>): bump version`,171 with NO `Co-Authored-By` trailer (overrides any default). The172 commit stays local.173174Draft release — never a duplicate:175176- `utils/*` packages and create-quasar get NO draft (no GitHub177 releases for them): they skip this whole section — say so when178 asking. The handoff below still applies, minus its draft item.179- Release label: ONLY the ui package is marked "Latest". GitHub does180 NOT persist a latest flag on drafts (it only applies at publish), so181 don't pass `--latest` flags when creating/editing the draft — the182 label is enforced at publish time by the handoff below.183- If a release for the tag already exists (`gh release view "<tag>"184--repo quasarframework/quasar --json isDraft` — finds drafts too):185 PUBLISHED -> stop, report the anomaly; DRAFT -> update it in place186 (`gh release edit "<tag>" ... --draft --title "<tag>"187--notes-file <file>`).188- Otherwise `gh release create "<tag>" --repo quasarframework/quasar189--draft --title "<tag>" --notes-file <file>` — tag and title are190 the full tag name; the body is the notes WITHOUT the leading tag191 line. A draft creates no tag (it is cut from dev HEAD at publish192 time).193194End the continuation by asking the user to run `pnpm publish` from195the package dir themselves (suggest the `! pnpm publish` prompt196prefix so its output lands in the session) — prepublish hooks run197builds/tests and may regenerate tracked files. NEVER run the publish198yourself.199200After the publish has run: if it left changes in the worktree, fold201them into the bump commit yourself without asking — `git add` them202and `git commit --amend --no-edit` (it stays a single commit; never203amend after the push) — then report what the commit now contains204(`git show --stat`) so the user sees exactly what they're pushing.205Then hand off:2062071. Push dev.2082. If a draft was created, give its link and how to publish it:209 `gh release edit "<tag>" --draft=false --latest=false` for any210 package except ui (publishing from the GitHub UI pre-selects211 "Set as the latest release" — uncheck it there); plain UI publish212 or `--latest` for ui.