minor-release

Source excerpt starting at line 1.

1---2name: minor-release3description: Write the changelog entry for a new minor or major Storybook release. Use when preparing a CHANGELOG.md entry for a X.Y.0 version.4allowed-tools: Bash, Read, Write, Edit5---6 7# Write Minor/Major Release Changelog8 9Assembles and writes a polished changelog entry for a Storybook minor or major (`X.Y.0`) release into `CHANGELOG.md`.10 11## Rules — read before doing anything12 13- **The two helper scripts are at `.agents/skills/minor-release/get-minor-changelog-summary.ts` and `.agents/skills/minor-release/write-minor-changelog-section.ts`. Do not search for them anywhere else in the repo. Do not look in `scripts/`, `package.json`, `AGENTS.md`, or elsewhere. Do not read the script source files. Just run them.**14- **Do not read `CHANGELOG.md` or `CHANGELOG.prerelease.md` before running the scripts.** The scripts handle version detection and entry collection automatically.15- **Do not read `CHANGELOG.md` for style guidance.** The style examples in Step 3 of this skill are the authoritative reference. Do not grep or read the changelog to infer format.16- Run all commands from the repository root.17 18## Step 1: Collect the changelog entries19 20Run the helper script to see all unique changelog entries from the prereleases, with patch-backported changes filtered out:21 22```bash23node .agents/skills/minor-release/get-minor-changelog-summary.ts [version]24```25 26- Omit `[version]` to auto-detect from the most recent prerelease in `CHANGELOG.prerelease.md`27- Pass `--verbose` to see which prerelease versions were found and how many patch PRs were filtered28- The output is a plain list of `- Entry text` lines, one per change29 30Read the output carefully — you will use these entries in Step 2 to choose highlights.31 32## Step 2: Select highlights33 34From the entries collected in Step 1, identify the **4–8 most significant changes** to feature as highlights. If fewer than 4 significant changes exist, include all available significant changes rather than padding the list with minor items. Good candidates:35 36- Major new features or capabilities37- New framework/ecosystem support (new renderer, builder, or major version support)38- Prominent DX or performance improvements39- Significant experimental features worth calling out40 41Exclude from highlights (they still belong in the full list):42 43- Bug fixes44- Maintenance, cleanup, dependency updates45- Minor improvements or internal refactors46- Reverts47 48## Step 3: Compose the highlights text49 50Based on the entries from Step 2, write the highlights section — the text that goes between the `## X.Y.0` heading and the full entry list. This is what you will pass to the write script. Follow the `Writing style` rules below.51 52### Writing style53 54The highlights text should contain only these parts, in order:55 56- An optional tagline line in the form `> _..._`57- One intro sentence58- One or more highlight bullet lists59 60Do not include the `## X.Y.0` heading — the script adds that.61 62The default format is:63 64```text65> _Tagline phrase_66 67Storybook X.Y [intro sentence]:68 69- 🔣 Highlight one: brief description70- 🔣 Highlight two: brief description71- 🔣 Highlight three: brief description72```73 74For releases with 7-8 highlights, a second group of bullets with its own intro sentence is fine (see 10.1.0 example).75 76**Style rules:**77- The tagline is wrapped in `> _italics_`. It is a short (5–10 word) noun phrase summarising the release theme — no verbs, no "we".78- Each highlight bullet: relevant emoji, feature/area name, brief description. Terse and specific.79- The intro sentence uses `Storybook X.Y contains hundreds of fixes and improvements including:` for most releases. For a major version, the intro is more impactful (see 10.0.0 example).80 81### Examples82 83**10.3.0** — a typical release with a single highlight group:84 85```text86> _Improved developer experience, AI-assisting tools, and broader ecosystem support_87 88Storybook 10.3 contains hundreds of fixes and improvements including:89 90- 🤖 Storybook MCP: Agentic component dev, docs, and test (Preview release for React)91- ⚡ Vite 8 support92- ▲ Next.js 16.2 support93- 📝 ESLint 10 support94- 〰️ Addon Pseudo-States: Tailwind v4 support95- 🔧 Addon-Vitest: Simplified configuration - no more setup files required96- ♿ Numerous accessibility improvements across the UI97```98 99**10.1.0** — a release with multiple highlight groups:100 101```text102> _Easier to setup, more accessible to use_103 104Storybook 10.1 focuses on two key improvements: installation and accessibility:105 106- ♿ UI overhaul to fix hundreds of a11y issues107- 🧑‍💻 CLI overhaul for faster, more reliable install108- ✅ Checklist-based onboarding guide for new users109 110The release also contains compatibility fixes for:111 112- 🅰️ Angular 21 support113- 🦀 RSbuild install support in CLI114- ⚡️ Preact support for Vitest addon115 116Finally, it contains two highly-requested experimental features:117 118- 📋 Component manifest for Storybook MCP119- ⚛️ Improved JSX code snippets for React120```121 122**10.0.0** — a major release with a more impactful intro (no `>` tagline, two-sentence intro):123 124```text125Storybook 10 contains one breaking change: it's ESM-only. This simplifies our distribution and reduces install size by 29% while simultaneously unminifying dist code for easier debugging.126It also includes features to level up your UI development, documentation, and testing workflows:127 128- 🧩 Module automocking for easier testing129- 🏭 Typesafe CSF factories Preview for React130- 💫 UI editing and sharing optimizations131- 🏷️ Tag filtering exclusion and configuration for sidebar management132- 🔀 Next 16, Vitest 4, Svelte async components, and more!133```134 135## Step 4: Write the changelog entry136 137Pass the highlights text to the write script via stdin. The script will call the summary script internally, combine the full entry list with your highlights, and write the complete section to `CHANGELOG.md` — inserting at the top or overwriting any existing section for this version.138 139```bash140node .agents/skills/minor-release/write-minor-changelog-section.ts [version] << 'HIGHLIGHTS'141> _Your tagline here_142 143Storybook X.Y contains hundreds of fixes and improvements including:144 145- 🔣 Highlight one146- 🔣 Highlight two147HIGHLIGHTS148```149 150Use `--dry-run` to preview the composed section before writing:151 152```bash153node .agents/skills/minor-release/write-minor-changelog-section.ts --dry-run << 'HIGHLIGHTS'154...155HIGHLIGHTS156```157