@williamthorsen/release-kit 10.5.0 → 10.7.0

package/.meta/changelog.json

@@ -0,0 +1,1570 @@
+[
+  {
+    "version": "10.7.0",
+    "date": "2026-09-15",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Fix scaffold error handling and cover every scaffolded workflow (#806)",
+            "body": "- Adds a `create-github-release.yaml matches template` check to release-kit's ReadyUp kit, which warns when `.github/workflows/create-github-release.yaml` differs from the template for the detected repo type and skips in a repo that has not installed that workflow.\n- Stops `v11y init --force` from replacing an existing `.config/v11y-check.config.json` with the defaults, which discarded the repo's thresholds and the allowlist maintained by `v11y sync`.\n\nMigration: To reset `.config/v11y-check.config.json` to its defaults, delete the file and run `v11y init`, because `v11y init --force` now overwrites only `.github/workflows/audit.yaml`.",
+            "migration": "To reset `.config/v11y-check.config.json` to its defaults, delete the file and run `v11y init`, because `v11y init --force` now overwrites only `.github/workflows/audit.yaml`.",
+            "hash": "1e197577c6c60678b5d6522f58b3211f3b10c752"
+          }
+        ]
+      },
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Gate the trusted-publisher checks on trust-query capability (#786)",
+            "body": "- Fixes the issue that the `npm-auto-publish` kit advised `npm trust github …` for every package when the npm session lacked the two-factor authentication that trust queries need.",
+            "hash": "255ac707f8eabbde2b14ce8ce5fb9819262f1b6e"
+          },
+          {
+            "description": "Treat label names that differ only in case as one label (#808)",
+            "body": "- Fixes the issue that `sync-labels generate` wrote a preset's `bug` and a local `Bug` to `.github/labels.yaml` as two labels, which made the first sync fail to create the second and every later sync rename the existing label back and forth.\n- Lets a `labels` entry change a preset label's casing: `Bug` replaces a preset's `bug` and appears in the output as `Bug`, and `Bug: null` removes it.\n- Makes `labels` keys that differ only in case a config error that names each group, such as `'bug' and 'Bug'`, since folding them would discard all but one without any sign in the output.\n\nMigration: Keep one of any keys in the `labels` record that differ only in case, and delete the others.",
+            "migration": "Keep one of any keys in the `labels` record that differ only in case, and delete the others.",
+            "hash": "e045010109b26aae95a63ad51d60c3eb688f5b6c"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Remove the redundant, soft-failing version read from release prepare (#811)",
+            "body": "- Deletes `readCurrentVersion` from `release-kit`, moving into `planVersionSet` the check that a `--set-version` target exceeds the current version and recording each workspace's version in the `DependencyGraph` passed to `propagateBumps`.\n- Stops prepare from printing a warning before it fails on an unreadable `package.json`, and replaces `failed to read current version` for a missing `version` under `--set-version` with an error from `planVersionSet` that reports the missing `version` field.",
+            "hash": "668123e01e71b013fa33dc391f9b0f685508a25b"
+          }
+        ]
+      },
+      {
+        "title": "⚙️ Tooling",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Upgrade eslint-config-typescript to v17 and adopt its ignore lists (#797)",
+            "body": "- Declares `vitest` as `catalog:` in every workspace that imports it, with the pnpm catalog pinning 4.1.11, because v17 no longer exempts `vitest` from `n/no-extraneous-import`.\n- Builds the global ignores in `eslint.config.ts` from the published `commonIgnores` and `toolIgnores`, which also exclude `pnpm-lock.yaml` and each `.readyup/manifest.json`, so the `eslint --fix` in `nmr lint` can no longer rewrite a kit manifest and make the next build's `rdy verify` fail.",
+            "hash": "b201669444763ad5bef85730b114098ef352e09b"
+          }
+        ]
+      },
+      {
+        "title": "📚 Documentation",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Trim the release-kit README and move reference detail into shipped docs (#802)",
+            "body": "- Adds `docs` to the published `files` of `@williamthorsen/release-kit` and a `!docs/*.v*.md` exclusion to both it and `@williamthorsen/nmr`, because `pnpm pack` would otherwise include the release-notes previews that a local checkout holds.\n- Adds `--version` to the options that `release-kit --help` lists, and points the hints for the removed `releaseNotes.shouldCreateGithubRelease` field at `release-kit init` instead of the README.",
+            "hash": "bce2e74071cffd44e64e8bf9e6d2e6a2adaaf363"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.6.0",
+    "date": "2026-09-08",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Report a package whose tarball would omit its changelog (#768)",
+            "body": "Adds ReadyUp checks to verify that every published package bundles its changelog files: the human-readable `CHANGELOG.md` and the machine-readable `changelog.json`.",
+            "hash": "25dd5c01b5e5b0ac26b266613fe71f47428e6c5c"
+          },
+          {
+            "description": "Add a migration field to changelog.json items (#770)",
+            "body": "Adds an optional `migration` field to entries in the `.meta/changelog.json` that `release-kit` generates. If a commit body contains a labeled migration step, that content is copied to the `migration` field.",
+            "hash": "a01f93f04e799a6e498b28e35a414349596c9d21"
+          }
+        ]
+      },
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Pin git-cliff and remove the per-run npx cache refresh (#776)",
+            "body": "Fixes an issue where git-cliff's version was unpinned, resulting in a per-run cache refresh. An exact version is now pinned.\n\nRemoves the per-run cache refresh, which re-ran `npx` without `--prefer-offline` once per prepare and forced a registry round trip. An exact version leaves npm nothing to revalidate, so a prepare run no longer waits on registry latency.\n\nAlso silences git-cliff's INFO output, in particular the crates.io update notice.",
+            "hash": "82acfde5405ee4c81ac8d8d4eca468722bad5ca4"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Remove the unwired isChangelogItem type guard (#771)",
+            "body": "Removes the unused `isChangelogItem` from `release-kit`'s `changelogJsonUtils.ts`, together with its tests.\n\nDocumentation is updated to record the boundary on `isChangelogEntry`: Entries parsed from `.meta/changelog.json` are shape-checked at the top level only, and strict validation applies only to the human-authored `.meta/changelog-overrides.json`.",
+            "hash": "f76ad8e6ebc852dc790e2dcdf874c1bb8aeb0245"
+          }
+        ]
+      },
+      {
+        "title": "🧪 Tests",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Read console spy output with listConsoleLines rather than by hand (#781)",
+            "body": "- Replaces the hand-rolled reads of a console spy's `mock.calls` in the `nmr`, `release-kit`, and `v11y-check` test suites with `listConsoleLines` from `@williamthorsen/toolbelt.vitest/candidate`.\n- Clears the `toolbelt.vitest/no-console-calls-read` recommendation that `rdy run --packages` reported.",
+            "hash": "9a5fbc2f01e8468821be89c345c59ade913074f4"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.5.0",
+    "date": "2026-09-01",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Report a consuming repo that still declares @changesets/cli (#764)",
+            "body": "Adds a check to the default ReadyUp kit in `@williamthorsen/release-kit` that reports a repo still declaring `@changesets/cli`, the release tool superseded by release-kit. The check reports at `recommend` severity; its fix directs the consumer to remove the dependency together with the `.changeset/` directory and any `changeset:*` scripts.",
+            "hash": "62f8a9ed0dc005ed84e066bf5d144ada9f3f69ae"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Upgrade to readyup v0.34 and exclude a private repo root from kit checks (#759)",
+            "body": "Upgrades `readyup` to v0.34, whose `discoverWorkspaces` now reports the repo root. `release-kit`'s `npm-auto-publish` kit filters that root out unless it is publishable, so a private root is no longer listed in the kit's report.\n\nTest suites for release-kit's ReadyUp kits have been refactored to use the patterns documented in v0.34.",
+            "hash": "2c0cf04c9a282e10e03c3fd1a44d4330b8a25a94"
+          },
+          {
+            "description": "Upgrade eslint-config-typescript and mark the discards it now reports (#761)",
+            "body": "Upgrades `@williamthorsen/eslint-config-typescript` to v12 and fixes violations surfaced by the newly added rule warning against a disposable that is discarded or that is bound to a declaration that never releases it.",
+            "hash": "61f59fe51681c590278f7c969bb3889309396dcc"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.4.4",
+    "date": "2026-08-24",
+    "sections": [
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Upgrade ReadyUp and the toolbelt packages, adopting their new APIs (#748)",
+            "body": "Upgrades `readyup` and the `@williamthorsen/toolbelt.*` packages to their latest versions.\n\nThe `readFile` utility from `readyup` replaces hand-rolled code in `nmr`.",
+            "hash": "9e54b0670c67b6b1da5d7afca7fe071ecbed2797"
+          }
+        ]
+      },
+      {
+        "title": "🧪 Tests",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Scaffold the temporary trees through the tree's own write API (#736)",
+            "body": "Scaffolds every `release-kit` test suite that holds a temporary tree through the tree's own write API rather than bare `node:fs`.\n\nAlso deletes `syncWorkTypes.unit.test.ts`'s wrapper `Disposable`, which restored a read-only tree's write permission before disposal; the pinned `@williamthorsen/toolbelt.filesystem` disposes such a tree on its own.",
+            "hash": "30d8125d1ce2c0660b4b03a1350b4f10deb31d0f"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.4.3",
+    "date": "2026-08-20",
+    "sections": [
+      {
+        "title": "🧪 Tests",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Register the working directory for disposal alongside the tree it points into (#724)",
+            "body": "Converts the `release-kit` and `v11y-check` suites that run from inside a temporary directory to `createTempTree` and `pointCwdAt`, registered through `disposeOnTestFinished` or scoped with `using`. Reverse-order disposal now restores the working directory before removing the tree it pointed into, which each suite previously had to sequence by hand.",
+            "hash": "6d3a42a33913ae9900b8a2d106329dcf690941e6"
+          },
+          {
+            "description": "Route the remaining hand-built temporary directories through createTempTree (#725)",
+            "body": "Replaces the hand-built temporary directories in the `release-kit` and `v11y-check` test suites with a `createTempTree` fixture, dropping the `beforeEach`/`afterEach` pairs that created and removed them.",
+            "hash": "92e76397f6f5ef3068b7f4805599fd090f930f7d"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.4.2",
+    "date": "2026-08-19",
+    "sections": [
+      {
+        "title": "🧪 Tests",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Register fixture-repo cleanup against the test that asks for it (#715)",
+            "body": "Routes nmr's `buildRepo` fixture helper through `createTempTree`, registering each fixture directory's removal against the test that requested it. The module-level accumulator and the exported `removeFixtureDirs` have been removed.",
+            "hash": "4186900691928b41e56b6f1855ca74b9700c1968"
+          },
+          {
+            "description": "Convert the per-test temporary directories to test-scoped fixtures (#719)",
+            "body": "Converts the suites that create a temporary directory in `nmr`, `nmr-core`, and `release-kit` to take it as a Vitest fixture built on `createTempTree`, or as a `using` declaration where the directory lives and dies inside one test body. Each suite loses the mutable binding and the `beforeEach`/`afterEach` pair that carried the directory's lifetime, and a directory is created only for the tests that name one.\n\nSeparately, `nmr lint:strict` now fails on a stale `eslint-disable` directive.",
+            "hash": "ab09827339799f3849b8968e7e25a9cd80083c30"
+          },
+          {
+            "description": "Register temporary-directory disposal where a helper holds the binding (#721)",
+            "body": "Routes the temporary directory through `createTempTree` in the `nmr` and `release-kit` test suites whose describe-local helpers hold its binding, and registers its removal with `disposeOnTestFinished`. The hand-written `afterEach` teardown goes; the binding stays, so no suite helper changes signature.",
+            "hash": "92f7a08621b7973595cb6401f98dd4f700770266"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.4.1",
+    "date": "2026-08-18",
+    "sections": [
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Accept `--only` under a project block, skipping the project release (#702)",
+            "body": "Fixes an issue where `release-kit prepare --only` exited with an error in any repo whose config declares a `project` block, which left the `only` dispatch input that `release-kit init` scaffolds into `release.yaml` unusable. A narrowed run now releases the named workspaces and skips the project release, reporting the skip and the selection that caused it as a warning.",
+            "hash": "d695171f77538a66373027a26ccb75e7e11cca87"
+          },
+          {
+            "description": "Route release-notes preview warnings through the prepare plan (#705)",
+            "body": "Fixes an issue where `release-kit prepare --with-release-notes` printed its diagnostics to stderr ahead of the release report, and described a skipped release-notes preview as a skipped README injection. The messages now render as `⚠️` lines inside the report and are worded for release-notes previews; a skip belonging to one workspace names that workspace.",
+            "hash": "47b0e025992e64bbb5b6a8ce951c5bb14b3d0315"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.4.0",
+    "date": "2026-08-17",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Let a project release cover repo-root paths (#685)",
+            "body": "Extends `release-kit`'s project release to a repo whose content lives at the root. Such a repo declares `project: { paths: ['**'] }` and gets the root `CHANGELOG.md`, the root `.meta/changelog.json`, the `--with-release-notes` previews under root `docs/`, the root `package.json` bump, and the project tag that the stage produces.\n\n`paths` scopes any project release's window, not only the whole-tree case, and the project tier of `release-kit validate-overrides` with it. A declared value replaces the workspace union rather than extending it; omitting `paths` resolves to that union, so existing consumers see no change.",
+            "hash": "75250fe6e61b596a265fff74ffadf1ffcf430579"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Adopt silenceConsole across the test suites (#677)",
+            "body": "Adopts `silenceConsole` from `@williamthorsen/toolbelt.vitest` to replace all hand-rolled `vi.spyOn(console, …)` spies and reduce boilerplate across the repo's test suites. The function returns a disposable, allowing the caller to use `using` to enable restoration of the console method at the end of the test scope.",
+            "hash": "412fd27cfe1324612aa123d1f8166fb6b37a07ff"
+          },
+          {
+            "description": "Adopt `isError` and consolidate errno narrowing on a shared helper (#697)",
+            "body": "Replaces every hand-rolled `instanceof Error` narrowing with `hasErrnoCode`, a new predicate exported from `@williamthorsen/nmr-core`, or with `isError` from `@williamthorsen/toolbelt.errors`. Previously the errno question was answered by inline copies alongside two private helpers of differing shape; both helpers are removed.\r\n\r\nSeparately, `eslint.config.ts` now bans `instanceof Error` in every position rather than in a ternary alone.",
+            "hash": "c5e8e8a5e006b451e8c5aeea75d35772926d503c"
+          }
+        ]
+      },
+      {
+        "title": "🧪 Tests",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Replace the stdio spies with captureStdio (#678)",
+            "body": "Replaces every `process.stdout` and `process.stderr` spy in the test suites with `captureStdio` from `@williamthorsen/toolbelt.testing` and deletes the obviated local capture helpers. `captureStdio` buffers writes rather than recording calls, so assertions that previously used `toHaveBeenCalledWith` instead check `stderr`/`stdout` strings and their chunk arrays.\n\nSeparately, `unicorn/no-nonstandard-builtin-properties` is off for test files. Its hand-maintained symbol table omits `Symbol.dispose`, which a suite-scoped capture calls to restore the streams, and `schema: []` offers no way to extend the table.",
+            "hash": "b59304680cd26864d282ec3b36eac31bc2e0386d"
+          },
+          {
+            "description": "Adopt throwOnProcessExit and captureError across the test suites (#690)",
+            "body": "Adopts `throwOnProcessExit` from `@williamthorsen/toolbelt.vitest`, replacing every hand-rolled `process.exit` mock in the `release-kit` and `nmr-core` test suites, and `captureError` from `@williamthorsen/toolbelt.testing`, replacing inline try/catch/`instanceof` blocks.\n\nSeparately, `@williamthorsen/toolbelt.vitest` is now listed in the ReadyUp config, so that its kit is run by `rdy run --packages`.",
+            "hash": "41a14bbee515d27ccb92058816eec46812a88478"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.3.2",
+    "date": "2026-08-13",
+    "sections": [
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Adopt toolbelt.errors for error-message extraction and cause-chaining (#652)",
+            "body": "Improves error reporting by adopting standardized ways of capturing and describing errors across the codebase.",
+            "hash": "30e6dac440ca7c61b8f44fb2998ff9e933425008"
+          }
+        ]
+      },
+      {
+        "title": "⚙️ Tooling",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Upgrade the lint config and clear its violations (#671)",
+            "body": "Upgrades `@williamthorsen/eslint-config-typescript`, along with other config packages, and clears lint violations surfaced by the newly activated rules.",
+            "hash": "17124c0ccd1a101d9fc46743b8e6b05d1e639e19"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.3.0",
+    "date": "2026-08-08",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Stop reporting absence checks that pass (#610)",
+            "body": "A ReadyUp check that checks for a problem (such as an unwanted file or a stale config reference) now stays silent unless it finds one. The `nmr`, `release-kit`, and `v11y-check` ReadyUp kits previously printed a line for every such check on every run.",
+            "hash": "aa4cbae89dfe4f6268ca4de318213fc3f610aba0"
+          },
+          {
+            "description": "Stop reporting non-issues in the readyup kits (#613)",
+            "body": "Modifies the `release-kit` and `nmr` ReadyUp kits to avoid verbose reporting when an initial check determines that further checks aren't applicable. In particular, a repo with no `release-kit` config file gets a single line in the `release-kit` report, and a repo that publishes nothing now bypasses the `npm-auto-publish` kit instead of failing it.",
+            "hash": "6ad37a6a9e8ae91403bfb92e74c1ab05c60d6e32"
+          }
+        ]
+      },
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Publish build output atomically so a failed build cannot destroy it (#631)",
+            "body": "Fixes an issue where a failed or still-running `nmr build` could leave a package with no build output at all, breaking the tooling that a subsequent build depends on. Separately, the error reported when a package's build output is missing now names the correct recovery command.",
+            "hash": "79ea249c38dfa265c4be6da57f8a340e54e578b8"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Retire the deferred-lint-rule list and enforce its rules (#628)",
+            "body": "Errors that `release-kit` rethrows now carry the original error as their cause, previously available only as message text. Help text and documentation for `--with-release-notes` now use the same placeholder notation for its output paths.\n\nAll violations of lint rules in the `release-kit` project are now cleared, and the list of deferred lint rules is retired, restoring associated rules to a max severity of \"error\" during strict linting.",
+            "hash": "dbafb8086d27b0ec5019a2a35b56fab7ce4ceae8"
+          }
+        ]
+      },
+      {
+        "title": "⚙️ Tooling",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Migrate to the shared tsconfig baseline (#626)",
+            "body": "Adopts `@williamthorsen/tsconfig` as the standard TypeScript configuration for this repo, replacing the previous hand-maintained copy. Reading a property through an index signature now requires bracket notation or a type that declares the property. The `nmr` build now fails on a base TypeScript config it cannot resolve, rather than building without it, and it now resolves a base config named by package name alone.",
+            "hash": "890a67c84b99d7efa663f8e64cf0beb89168581b"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.2.2",
+    "date": "2026-08-05",
+    "sections": [
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Report the missing npm login once, not per package (#598)",
+            "body": "Fixes an issue where running release-kit's publish-readiness checks without an npm login reported a trusted-publisher failure for every published package. The missing login is now reported once, with `npm login` as the fix. An unreachable registry now has its own check. The trusted publisher check produces more informative failure messages.",
+            "hash": "47e8dd774b617ebc6095c7fc0c9b5e8e0a0de883"
+          },
+          {
+            "description": "Make prepare all-or-nothing and report the tags file by path (#601)",
+            "body": "Fixes an issue where a failed `prepare` could leave the release flow in a broken intermediate state. A release now lands completely or not at all, and a formatting failure no longer discards one that already landed. When a write fails partway, the error names every file that reached disk, every file that did not, and the commands that undo them.\r\n\r\n`commit` and `tag` now report the full path of the tags file they looked for, and distinguish a missing file from one that could not be read, so that running from the wrong directory or worktree is no longer reported as a release that never happened.\r\n\r\nRuns with `--with-release-notes` now list the preview files they write, and `--dry-run` names the ones a real run would write.",
+            "hash": "83ac6e45cf9d4b5371650cda42d7830ed4988660"
+          }
+        ]
+      },
+      {
+        "title": "🧪 Tests",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Clear the deferred vitest test rules and enforce them (#602)",
+            "body": "Fixes a subset of previously deferred lint violations and restores the severity of Vitest lint rules to \"error\" for purposes strict linting.",
+            "hash": "4b43d29580fe9736fb2b4fa4ae6c2348cca53754"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.2.1",
+    "date": "2026-08-04",
+    "sections": [
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Remove the 1 MiB ceiling on captured git output (#596)",
+            "body": "Fixes an issue where `release-kit prepare` began aborting once a repository's release history grew long enough, leaving that repository unable to cut another release. The fix covers, in addition to `prepare`, every other release-kit command that reads from git.",
+            "hash": "07bf786d00c493f7bc4c0fda6932ea9659ca6f95"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.2.0",
+    "date": "2026-08-04",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Add status labels and clear grouped-label descriptions (#585)",
+            "body": "Adds two status labels (`status:blocked` and `status:on-hold`) to the common preset and removes descriptions from other scoped labels (`priority:` and `value:`) to keep scoped groups compact in the GitHub UI.",
+            "hash": "98210d58895462431a8b08dbda30768b58d97633"
+          },
+          {
+            "description": "Publish each package's readyup kit from the package that owns it (#590)",
+            "body": "ReadyUp checks for `@williamthorsen/nmr`, `@williamthorsen/release-kit`, and `v11y-check` are now run directly against these packages, guaranteeing a version-appropriate check, instead of against their host repo. The package must be installed as a direct dependency in the calling repo.\n\nThe syntax is `rdy run --from npm:<package>`. `rdy run --packages` runs the kits contained in any packages listed in `.config/readyup.config.ts`. Requires `readyup` 0.23 or later.",
+            "hash": "f0fa3b416564ed4490c48007453fcb20c04807b3"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.1.0",
+    "date": "2026-08-03",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Publish nmr's readyup kit with a test-tier conformance check (#580)",
+            "body": "`@williamthorsen/nmr` is now bundled with ReadyUp kits that check a repo's alignment with `nmr` requirements and recommendations.\n\n`rdy run --from npm:@williamthorsen/nmr` checks the repo against the kits without prior configuration. Once the package is added to the ReadyUp config, `rdy run --packages` will run the `nmr` kits along with those of any other registered package. Requires `readyup` v0.23 or greater.",
+            "hash": "94bd46acfecf87d6ec0f981ee561c0ebf22d9c09"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Load the config with Node's TypeScript support instead of jiti (#573)",
+            "body": "`release-kit` now uses native Node with type-stripping to read its configs. `jiti` is no longer needed as a dependency. As a result, relative imports inside `.config/release-kit.config.ts` now require an explicit file extension.",
+            "hash": "b4837030475b6a65023001b31eeb746b6439eac3"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "10.0.0",
+    "date": "2026-08-03",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Retire integration label in favor of an isolation-tier test ladder (#552)",
+            "body": "Test groups are now named for what a test reaches rather than for how much of the codebase it covers: `integration` and `app` are replaced by `unit`, `tool`, `localhost`, and `remote`.\n\n`nmr test` now runs the `tool` group alongside `unit`, so the first run after upgrading may fail on tests that nothing was running before. Upgrading means renaming `*.int.test.ts` files onto the new groups and replacing `nmr test:integration` with `nmr test:tool`.",
+            "breaking": true,
+            "hash": "81f16694dc295c754d35e692eedd75f47be35f4d"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Move defineConfig to a dedicated config subpath (#566)",
+            "body": "`defineConfig` now comes from the `@williamthorsen/release-kit/config` subpath rather than from the package root. The subpath also carries the config types.",
+            "breaking": true,
+            "hash": "e0769815f41c23d64302be26c8369209fad72e22"
+          },
+          {
+            "description": "Share nmr-core's cache primitives with nmr-compile (#570)",
+            "body": "A package's writes to the build cache are now hidden from other packages until the write is complete. A failing build now reports its error in the same form as every other `nmr` command. `tsx` is no longer required to build a package.",
+            "hash": "2a67cf1e6181cb8713de485859c3731e16edacf6"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "9.1.0",
+    "date": "2026-07-31",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Make label descriptions optional and generate none for scope labels (#539)",
+            "body": "`release-kit` now supports labels without a description, and `release-kit sync-labels init` generates scope labels without one. Applying a label without a description clears any existing description the repository carries for that label.",
+            "hash": "275108cfbc5694647a945de5aa75ac0ac6d07152"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "9.0.1",
+    "date": "2026-07-30",
+    "sections": [
+      {
+        "title": "⚙️ Tooling",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Adopt Vitest projects in this repo (#530)",
+            "body": "Simplifies test configurations so that every package exposes the same test commands, which select suites by test category: `nmr test` runs everything except integration tests, `nmr test:integration` runs only those, and `nmr test:all` runs both. `nmr test:integration` now succeeds in a package that has no integration tests instead of failing. release-kit's drift checks can now be run on their own, apart from unit and integration tests. A fresh clone now has to run `pnpm run bootstrap` before any test run, not just before `nmr` commands.",
+            "hash": "a2fdd9c03c419f8fb70941ff5a3c580a6badcde6"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "9.0.0",
+    "date": "2026-07-28",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Unify label configuration in release-kit.config.ts (#505)",
+            "body": "Repositories now declare their label set alongside the rest of their release-kit configuration in `.config/release-kit.config.ts`, and the declaration is validated and completed in the editor as it is written. A label supplied by a bundled preset can now be recolored, reworded, or dropped. `sync-labels generate --check` now reports when the committed label file has fallen behind the declaration, writing nothing. The standalone `.config/sync-labels.config.ts` is no longer read; while it remains in place, every `sync-labels` command refuses to run, naming what to move and where.",
+            "breaking": true,
+            "hash": "d774ce4efc98e5a6f0c30f46c765c30fbfeed539"
+          }
+        ]
+      },
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Include commits scoped to `*` in the changelog (#496)",
+            "body": "Fixes an issue where commits scoped to `*` raised the version but were silently dropped from the generated changelog.",
+            "hash": "a449b394dc08a9d04e498afad6a058177a8af881"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "8.1.0",
+    "date": "2026-07-22",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Make label deletions reviewable and apply labels on merge (#493)",
+            "body": "Pull requests that touch a repository's label file now get a check listing every label change the sync would make, including deletions of labels the file never mentions, which a diff of the file cannot show. Merging the pull request now applies those labels. The sync's deletion and rename handling now changes only through a reviewed upgrade to a verified release. Repositories that already scaffolded this workflow adopt the new triggers by re-running `release-kit sync-labels init --force`.",
+            "hash": "05e9acec4c503b35e96906913f8a97c6875e9106"
+          }
+        ]
+      },
+      {
+        "title": "📦 Dependencies",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Upgrade dependencies and align the Node support policy (#483)",
+            "body": "All four published packages (`nmr`, `nmr-core`, `release-kit`, and `v11y-check`) now require Node.js 24 or later, up from Node 18.17. Separately, `nmr-compile` now rebuilds when the TypeScript version changes.",
+            "hash": "3090aa1ec68224f88e0b537ae09282e8e636f711"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "8.0.1",
+    "date": "2026-07-18",
+    "sections": [
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Skip private packages cleanly in publish and create-github-release (#477)",
+            "body": "Fixes an issue where a workspace marked private in its `package.json` could break a release: `release-kit publish` failed on it, and `release-kit create-github-release` created an unwanted public GitHub Release for it. Both commands now skip private workspaces cleanly: publish reports the skip and continues instead of failing the run, and create-github-release produces no Release for a private package. Any publishable packages released alongside it still publish and still get their Releases. Marking a workspace private is now all it takes to exclude it from both publishing and GitHub Releases.",
+            "hash": "d1a647c648a64f81d884c31e9c6e63b91b029687"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "8.0.0",
+    "date": "2026-07-13",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Fail a package that declares types but ships none (#467)",
+            "body": "`nmr attw` now fails a package that claims to ship type declarations but ships none. Such a package used to pass, leaving every TypeScript consumer of it silently typed as `any`.\n\n  A package that ships working declarations found only by sitting beside its JavaScript entry point escapes the check, since it declares nothing. Add a `types` entry to bring it under the check.",
+            "breaking": true,
+            "hash": "8ccea9d93cd63a7963a7a7516e20f8d54069bd7b"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "7.0.0",
+    "date": "2026-07-01",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Rebuild nmr-compile on a unified tsc emit (#455)",
+            "body": "`nmr` now compiles a package's JavaScript and type declarations in one step, rewriting every import form — static, re-export, dynamic `import()`, bare side-effect, and tsconfig `paths` aliases — to runnable `.js` in both outputs. It now requires TypeScript 5.7 or newer as a peer dependency.",
+            "breaking": true,
+            "hash": "0e55822c88cad341f90b052b15fb9af41e7ae414"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "6.0.0",
+    "date": "2026-06-30",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Rewrite parseArgs on node:util with typed error and exit API (#428)",
+            "body": "`@williamthorsen/nmr-core` gains a typed error API for CLI parsing: `parseArgsOrExit` (parse, or print a usage error and exit) and `ParseError` replace the per-command boilerplate, so every bundled CLI reports a flag mistake the same way. Breaking: the `translateParseError` export is removed and `parseArgs` now throws `ParseError`.",
+            "breaking": true,
+            "hash": "5629bef8f645485b401a04f06ff9153ef5472282"
+          },
+          {
+            "description": "Auto-activate integration test variant from config presence (#448)",
+            "body": "A package can now separate its integration tests from its standalone suite simply by including a `vitest.integration.config.ts` (alongside a `vitest.standalone.config.ts`). The `--int-test` flag that previously enabled this is removed — that config-file pairing is now the only way to activate the separation. In such a package, `test` and `test:coverage` run only the standalone suite and skip integration tests, while a new `test:all` runs both suites together. The separation now holds even when tests run across every package at once, so a full-workspace `test` run still keeps integration tests out of the default suite. Packages that previously hand-copied these test scripts no longer need to.",
+            "breaking": true,
+            "hash": "ee320b913ef1d7255c78eef6fc9ab3b9e94dfd39"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Route all CLI error reporting through a single stderr helper (#437)",
+            "body": "Consolidates error reporting across the CLIs so every command reports errors the same way, and guards against the previous inconsistency returning. The error messages and exit codes users see are unchanged.",
+            "hash": "63e36b3f80bd8858e940362ea2914cb9a19fd821"
+          },
+          {
+            "description": "Normalize CLI error wording to the canonical Error: format (#439)",
+            "body": "Single-line error messages from the `nmr` and `release-kit` commands now print in one uniform shape, so the same class of failure reads the same way no matter which command produced it. Previously the wording varied, which made error output harder to scan and harder for scripts to match against. Richer output, such as multi-line validation reports and the stack trace from an unexpected crash, is unchanged.",
+            "hash": "2cbb46523fc7c3f0d8387405cafbd2cc90274b19"
+          },
+          {
+            "description": "Consolidate prepare parsing onto parseArgsOrExit (#441)",
+            "body": "Makes `release-kit`'s `prepare` command report invalid arguments the same way its other commands already do. The error message and exit code a user sees for a bad argument are unchanged.",
+            "hash": "f314f9c0fb8eacbe4f44a56951075a61604aaa0c"
+          },
+          {
+            "description": "Unify prepare help text into a testable module (#443)",
+            "body": "Running `release-kit prepare --help` now lists the complete set of options. The `--force` flag and the restriction that `--set-version` and `--only` cannot be used when a project block is configured were previously missing from the help and are now shown there; the same `--set-version` restriction was added to the package README's `prepare` reference.",
+            "hash": "0da311a5516e92cfa18dc9dbd642efb5645847c8"
+          }
+        ]
+      },
+      {
+        "title": "📚 Documentation",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Document single-package --force rejection in release-kit prepare (#450)",
+            "body": "The `release-kit prepare` `--force` documentation now correctly describes per-mode behavior: a bare `--force` is rejected in a single-package repo, where an explicit `--bump` level must be passed, while the \"defaults to patch\" shortcut applies only in monorepo and project mode.",
+            "hash": "8924e37b31f21be5cf0c19e393be2269ea2281f4"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "5.4.0",
+    "date": "2026-06-27",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Centralize the per-package build as an nmr-compile bin (#419)",
+            "body": "Introduces `nmr-compile`, a single command shipped with `@williamthorsen/nmr` that compiles each workspace package and now backs the default build. Consuming repos can delete their own per-package build script and pick up future build fixes just by upgrading nmr. Repeated builds with unchanged source now reliably skip recompiling instead of occasionally rebuilding for no reason, and import aliases now resolve correctly in symlinked checkouts.",
+            "hash": "cc20e3130087689c2fe8bf0e6de4b1349646296e"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "5.3.2",
+    "date": "2026-06-16",
+    "sections": [
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Migrate from js-yaml to yaml (#410)",
+            "body": "Replaces the `js-yaml` dependency with the `yaml` package for all YAML reading and writing, with no change to behavior or generated output. The swap trims the dependency footprint by dropping a direct dependency and its companion type-definitions package, since `yaml` ships its own types.",
+            "hash": "fec315ab67e6d5c4b7eac3cb908c7c83a323f17c"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "5.3.1",
+    "date": "2026-05-19",
+    "sections": [
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Validate overrides against the full release history (#401)",
+            "body": "Fixes an issue where `release-kit overrides validate` reported overrides as stale when they targeted commits in past releases, even though `release-kit prepare` correctly matched them. The two commands now agree on which overrides are stale.",
+            "hash": "eee4dd1a7fd2d8268ec10183372398dd46fb58d1"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Restructure tests and align core package directory with package name (#405)",
+            "body": "Tests in every package are now typechecked alongside the code they cover, so type breakage in tests fails the build instead of slipping through. The `core` package's workspace directory is renamed to match its package name, so `nmr -F nmr-core ...` and `pnpm --filter nmr-core ...` now resolve where they previously failed.",
+            "hash": "91006ec4281be902d66dfdef3917f603ee56b5c3"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "5.3.0",
+    "date": "2026-05-10",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Enable editorial overrides for changelog entries (#387)",
+            "body": "Allows `release-kit` consumers to skip or correct historical changelog entries by means of an overrides file.",
+            "hash": "e9eb4392e69550985e1ec2beb0529a5a2b837165"
+          },
+          {
+            "description": "Decentralize changelog overrides to per-scope .meta/ files (#391)",
+            "body": "Adds support for workspace-scoped editorial-override files for `release-kit`-generated changelogs. A repo-root file applies overrides to every workspace's changelog; a workspace-tier file applies only to that workspace.",
+            "hash": "016df352eb8fee40665a958db136f5e5deeb6a42"
+          },
+          {
+            "description": "Add section markers and authenticated upstream fetch (#393)",
+            "body": "A new `markers` block in `work-types.json` describes the breaking-changes emoji and label, making them available for use by consumers.\n\n`work-types check` and `work-types sync` now authenticate when `GITHUB_TOKEN` is set, so they can reach private upstream repositories.",
+            "hash": "402e559e81902ac41b4206f866717524951b1cd1"
+          },
+          {
+            "description": "Validate changelog overrides from the command line (#395)",
+            "body": "Adds a `release-kit overrides validate` subcommand that audits every `.meta/changelog-overrides.json` file across the project root and per-workspace scopes in one pass. The command reports schema errors, ambiguous-prefix collisions, and stale-key warnings with tiered exit codes so CI can choose its own failure threshold. The same validation is also available via a library function exported by the package.",
+            "hash": "d9bdd62a3ef47fe06a07723269e9dabdd058d574"
+          }
+        ]
+      },
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Suppress git-cliff stale-version warnings on prepare (#373)",
+            "body": "Fixes an issue where `release-kit prepare` repeatedly printed git-cliff's \"A new version of git-cliff is available\" notice — twice per release unit, so 2 × N times for an N-package monorepo run — while never updating the locally cached git-cliff binary. Each `prepare` run now revalidates the npm cache once before any cliff work, so the binary stays current with upstream releases and the notice no longer surfaces on every per-workspace invocation.",
+            "hash": "8660d3917a11c40f4d57bf64dca740b947b7fc69"
+          },
+          {
+            "description": "Use synthetic changelogs for forced empty-range releases (#376)",
+            "body": "Fixes an issue where `release-kit prepare` with `--force`, `--bump=X`, or `--set-version` would invoke git-cliff against units that had no commits since their last tag, surfacing confusing `WARN  git_cliff > There is already a tag (...)` lines (twice per affected unit) and silently leaving `CHANGELOG.md` and `.meta/changelog.json` stale. Empty-range bumps now write a synthetic `Notes / Forced version bump.` entry to both files instead of invoking git-cliff. Applies to all three release stages: single-package, per-workspace, and project. Prior changelog history is preserved on every path.",
+            "hash": "cb118b2f06d52ceb375192352fa158d976dcbe4f"
+          },
+          {
+            "description": "Accept `breakingPolicies` field in config files (#394)",
+            "body": "Fixes an issue where setting `breakingPolicies` in `release-kit.config.ts` was rejected as an unknown field, leaving per-work-type breaking-policy configuration unreachable from the config file. Each entry accepts `'forbidden'`, `'optional'`, or `'required'`; an empty object opts out of enforcement.",
+            "hash": "4c663f8dec7800810f4c0350ef4b661978505acb"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "5.2.1",
+    "date": "2026-05-05",
+    "sections": [
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Soft-skip tags with no changelog entry under --tags (#366)",
+            "body": "Fixes an issue where `release-kit create-github-release --tags <tag>` exited 1 — failing the calling CI workflow — when the requested tag had no changelog entry. Tooling-only releases (those whose changelog generator legitimately omits an entry) are now soft-skipped with an info-level summary, the same as releases skipped because their entry has no audience-relevant content. Typo protection is preserved: passing an unknown tag to `--tags` still exits 1.",
+            "hash": "a79c5b402215376e36aa006c12d8585452db3aa8"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "5.2.0",
+    "date": "2026-05-04",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Add emojis to changelog and release-note headings (#352)",
+            "body": "Adds emoji prefixes to the section headings rendered in `CHANGELOG.md` and release notes generated by `@williamthorsen/release-kit`. Each of the 13 default work types gets a single decorative emoji so its section is easier to spot when skimming a release: 🐛 Bug fixes, 🎉 Features, 📚 Documentation, ♻️ Refactoring, ⚡ Performance, 🔒 Security, 🧪 Tests, ⚙️ Tooling, 👷 CI, 📦 Dependencies, 🏗️ Internal, 🗑️ Deprecated, and 🤖 Agentic support. Matching of `changelogJson.devOnlySections` is emoji-tolerant: existing consumer overrides written as bare names continue to work without modification.",
+            "hash": "07115bb4324bb605d5b527baf9dcf0b8a1dd9f4d"
+          },
+          {
+            "description": "Surface bang violations in release prepare reports (#359)",
+            "body": "Release-prepare flows now surface `!`-policy violations as warnings in the prepare report. Each workspace's and project's commit window is parsed against the default policy table — `internal!` is rejected as contradictory, bare `drop:` is rejected for missing the required `!`, and so on — and any violations appear under the workspace's section in the report alongside short hash, truncated subject, type, and surface (prefix or body). A new `breakingPolicies` config field lets consumers override individual entries or pass `{}` to disable enforcement entirely. Release-time enforcement remains tolerant: violations are warnings, never failures, so a single legacy commit cannot block a release.",
+            "hash": "6a6ed5558ac91c1e1e0bee5a9b5bb3d01111a8b0"
+          }
+        ]
+      },
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Restrict publish to publishable workspaces (#345)",
+            "body": "Fixes an issue where `release-kit publish` failed for workspaces marked `package.json#private: true`. The command now operates only on publishable workspaces — those where `private` is absent or `false` — and the rest of the release pipeline (`tag`, `create-github-release`, `prepare`, changelog) continues to handle private workspaces unchanged. This preserves the \"versioned but not published\" workflow: a private workspace can still be versioned, tagged, and published as a GitHub Release; only the registry-publish step is skipped. Without `--tags`, unpublishable tags are silently filtered (an empty result prints `Nothing to publish.` and exits 0). With `--tags` naming an unpublishable workspace, `release-kit publish` exits 1 with one error per offending tag, citing `package.json#private` and the workspace path.",
+            "hash": "aee2c1aa1822dedc7349b03506f3a63bb95d4175"
+          },
+          {
+            "description": "Skip tooling-only releases instead of failing (#347)",
+            "body": "Fixes an issue where `release-kit create-github-release --tags <tag>` exited 1 whenever the tag's changelog had no all-audience content. The reusable `create-github-release.reusable.yaml` workflow forwards `github.ref_name` into `--tags`, so tooling-only releases consistently produced failed workflow runs even though no failure occurred. The command now exits 1 only when a requested tag has no changelog entry; intentional skip reasons (`no-audience-content`, `empty-body`) are informational. A typoed tag still surfaces an error even when batched alongside successful tags, and the info summary reports the per-tag skip reason for diagnostic visibility.",
+            "hash": "5e674139fe8f884b7b03dff3f798c56ae089b03d"
+          },
+          {
+            "description": "Establish canonical work-types SSOT and restore changelog section ordering (#358)",
+            "body": "Restores canonical section ordering in changelogs and release notes — sections were appearing in unpredictable order after the previous release added emoji prefixes to section headers. Sections now follow a stable priority: public-facing types (Features, Fixes, Security, …) first, then internal types, then process types. Release-note bullets for breaking changes carry a `🚨 **Breaking:**` prefix so they stand out at a glance. Documentation entries move out of public release notes — they continue to appear in dev changelogs.\n\nCloses #355.",
+            "hash": "7f2c569a4840300e2cce8fe5aa7ab65fa2f9b5a1"
+          }
+        ]
+      },
+      {
+        "title": "⚡ Performance",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Skip npx registry revalidation when running git-cliff (#361)",
+            "body": "Speeds up `release-kit prepare` by skipping the npm registry cache-revalidation HTTP request that ran on every `git-cliff` invocation. Per-invocation overhead drops from ~4.6 s to ~2.0 s; in a four-workspace monorepo this saves about 10 seconds per run. Also suppresses a transient stderr spinner that briefly appeared during package resolution and looked like a half-complete log message. Network fallback is preserved — runs on machines with an empty npx cache still resolve `git-cliff` over the network.",
+            "hash": "74d2a70b2ef70311f356d104966997a4890d5d11"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Read package version at runtime via shared helper (#338)",
+            "body": "Fixes an issue where running `audit-deps`, `nmr`, or `release-kit` from the locally built `dist/esm/` after a `git pull` could report a stale version. Each CLI now reads its version directly from its `package.json` at startup, so version reads stay in sync with the installed source without requiring a fresh `pnpm install` or rebuild.",
+            "hash": "0fc98bb70d458d8eb5727d9567e3e20a8f2ded00"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "5.1.0",
+    "date": "2026-04-30",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Add `project` block for project-level release stage (#317)",
+            "body": "Adds support for monorepos that ship a single combined deliverable to version, changelog, and release-note the project itself rather than only its constituent workspaces.",
+            "hash": "f647df54e78b9c78673874c7a5e197b87c562361"
+          },
+          {
+            "description": "Publish JSON Schema for `.meta/label-map.json` (#325)",
+            "body": "Adds a JSON Schema for `.meta/label-map.json` to release-kit, packaged at `packages/release-kit/schemas/label-map.json` and shipped to npm. Consumers reference it via the stable raw URL pattern `https://github.com/williamthorsen/node-monorepo-tools/raw/release-kit-v<version>/packages/release-kit/schemas/label-map.json` — the same shape audit-deps already uses.",
+            "hash": "1c0fb5036cc222d15aaa547fb5a8b2bd74d8d34f"
+          },
+          {
+            "description": "Label prepare errors with the failing stage (#326)",
+            "body": "Adds stage attribution to errors thrown during `release-kit prepare`. Errors from per-workspace bumps and changelog generation, the project release stage, and the post-release format command now begin with a stage label that identifies the failing stage and (where relevant) the affected workspace.",
+            "hash": "feb1c81c912d40b4f1fd4b8037277636eee09e39"
+          },
+          {
+            "description": "Make `--force` and `--bump` orthogonal (#328)",
+            "body": "Decouples `--force` and `--bump` so each flag has a single responsibility, and unifies skip semantics across the per-workspace and project pipelines.",
+            "hash": "6927677759e464dcfcab778fdade4bf875a98fb4"
+          }
+        ]
+      },
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Make publish's clean-tree safety gate reachable (#311)",
+            "body": "Fixes an issue where `release-kit publish` failed with pnpm's \"working tree is dirty\" error on a clean tree whenever `releaseNotes.shouldInjectIntoReadme: true` was configured. release-kit injects the release notes into the package README before invoking `pnpm publish`, so pnpm's own working-tree check fired on a tree release-kit had just dirtied — even though the user's tree was clean at command start.",
+            "hash": "cbad5104a6f6af5fd664ae5bca526f1d00b9eaa9"
+          },
+          {
+            "description": "Make `--set-version` + `project` rejection explicit (#319)",
+            "body": "Improves the error users see when invoking `release-kit prepare --set-version` with a `project` block configured. The combination is still rejected — as before — but now produces a single, project-aware message (\"--set-version cannot be combined with a project release…\") rather than the previous two-step chain (`--set-version requires --only`, then `--only cannot be combined with a project release` after the user added `--only`).",
+            "hash": "d6500855a6a7fce87b881bbeabc5493a41af8cc9"
+          },
+          {
+            "description": "Reject `--only` that would strand excluded dependents (#321)",
+            "body": "Fixes a silent footgun in `release-kit prepare --only=...`: an excluded internal dependent with its own changes would be left unreleased with no runtime signal, even though the targeted workspace it depends on was being released. The command now rejects such invocations up front, naming every excluded dependent whose changes would be stranded.",
+            "hash": "64118ef22097aa2fd4aa05980d15c432698498a3"
+          },
+          {
+            "description": "Order prerelease versions correctly in changelog sort (#334)",
+            "body": "Fixes a latent issue in `@williamthorsen/release-kit` where prerelease version tags (e.g., `1.2.3-alpha`, `1.2.3-rc.1`) were sorted as if their prerelease component were absent, causing them to appear in the wrong position relative to releases sharing the same base version. Changelog entries are now ordered per SemVer §11: prerelease versions precede the corresponding release (`1.2.3-alpha < 1.2.3`), build metadata is ignored for ordering, and entries that fail SemVer validation sort deterministically to the bottom of the list rather than collapsing into mid-list positions.",
+            "hash": "5c0df1d9ecdfcf6cf7154758310239c3f856f0e5"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Convert prepare results to discriminated unions (#330)",
+            "body": "Tightens `ProjectPrepareResult` and `WorkspacePrepareResult` from flat-with-optionals types into status-discriminated unions, so consumers that have already narrowed on `status === 'released'` no longer need to re-guard each release-only field with `!== undefined`. The four new sub-types (`ReleasedProjectResult`, `ReleasedWorkspaceResult`, `SkippedProjectResult`, `SkippedWorkspaceResult`) are exported from the package so callers can name the variants directly. Renderer output is byte-identical to before.",
+            "hash": "0b41e3ad9809ce8659f766cb7578287a5918336c"
+          },
+          {
+            "description": "Split changelog.json generation into layered helpers (#333)",
+            "body": "Reorganises `changelog.json` generation in `@williamthorsen/release-kit` so that producing entries (running git-cliff and shaping the output) is fully separated from persisting them (reading, merging, and writing the file). Removes the silent-discard parse-failure path at the project release stage by no longer reading the root `changelog.json` before overwriting it. Sharpens dry-run mode: `git-cliff` now runs even on dry-run so configuration mistakes surface in preview rather than only on a real release. Trims the public `index.ts` barrel from ~50 re-exports to the two type names actually consumed by external configs.",
+            "hash": "ce99578aeafbcb333d6e750ed7028e190f8f06bf"
+          }
+        ]
+      },
+      {
+        "title": "🧪 Tests",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Cover untested project-release and config branches (#329)",
+            "body": "Closes four mechanical test-coverage gaps in the project-level release surfaces flagged in the test review of #308. New cases exercise the `(no previous release found)` rendering for released projects, the unparseable-commit warning block on the released-project rendering path, the `readFileSync` I/O failure path in `readRootPackageVersion`, and the contributing-paths invariant in `releasePrepareProject`. No production code changes — these are pure-render and pure-derivation branches that previously had no test exercising them.",
+            "hash": "d4473292bee1e0f33bc6d9c4698c84df21209f6d"
+          }
+        ]
+      },
+      {
+        "title": "📚 Documentation",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Document tag prefix collisions as general rule (#320)",
+            "body": "Documents the strict-prefix tag-prefix collision rule as a general validation rule that applies to every release-kit consumer declaring more than one tag prefix: across active workspaces, declared legacy identities, retired packages, and the optional `project` block. Previously, the rule appeared only inside the `Project releases` validation list.",
+            "hash": "01b7c6524a55e237b96463312d04a5193c05a494"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "5.0.0",
+    "date": "2026-04-23",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Improve release-notes rendering quality (#261)",
+            "body": "Improves the quality of release notes and CHANGELOG entries generated by release-kit. Release notes sections are now ordered by work-type priority (bug fixes first, then features, then internal), and each bullet now includes the commit body text for context that a one-line title cannot provide. Refactoring commits are now excluded from the release notes.",
+            "hash": "f42b1bc44e48f600131c56d9e86a7a721807788f"
+          },
+          {
+            "description": "Scaffold release-notes injection and check markers (#267)",
+            "body": "Adds release-notes injection to the configs scaffolded by `release-kit init`, so newly-onboarded consumers get the feature without having to discover or toggle the flag. The release-kit readyup kit gains a check that warns when a consumer's README is missing the marker pair where injected notes should land — without those markers, injection silently prepends to the top of the file, pushing the README's title below the notes.",
+            "hash": "7e87590c9cb73d3feb48701af8df0e368b55a7d3"
+          },
+          {
+            "description": "Split GitHub Release creation into its own workflow (#272)",
+            "body": "Splits GitHub Release creation out of release-kit publish into a dedicated release-kit create-github-release CLI command and a matching reusable GitHub Actions workflow. Consumers that do not publish to npm can now create Releases independently, and the contents: write permission required to create a Release no longer leaks into the publish path.",
+            "breaking": true,
+            "hash": "20ff00c2308098a9dcd5dfefc99d56b7c7a7f752"
+          },
+          {
+            "description": "Replace --only with --tags on release-kit publish and push (#273)",
+            "body": "`release-kit publish` and `release-kit push` now filter by full tag name via `--tags=<tag1,tag2>` instead of workspace directory name via `--only=<dir>`, matching the shape already used by `create-github-release`. Callers pass the tag they care about (e.g., `core-v1.3.0`) directly, with no translation step back to the publishing workspace's directory name. The reusable workflow gains an optional `tags:` input, and the internal `publish.yaml` caller now passes `tags: ${{ github.ref_name }}`, making the publish scope explicit rather than relying on the single-tag fetch default of `actions/checkout@v6`.",
+            "breaking": true,
+            "hash": "eb66c865fcaacb343e236fb1bee67fe25550e0ae"
+          },
+          {
+            "description": "Apply pre-1.0 bump rule and add --set-version CLI escape hatch (#274)",
+            "body": "Fixes an issue where a `feat!` commit on a pre-1.0 package would accidentally promote it to `1.0.0`. At pre-1.0 (`0.y.z`), a `'major'` release type now collapses to a minor bump. Adds a validated `--set-version <semver>` CLI flag on `release-kit prepare` that bypasses commit-derived bump logic and writes a specific version.",
+            "hash": "121dabc7ca690372fea8a6c33a298d760cfe40f4"
+          },
+          {
+            "description": "Scaffold audit.yaml workflow from audit-deps init (#277)",
+            "body": "Adds GitHub Actions workflow scaffolding to `audit-deps init`. Running the command now writes both `.config/audit-deps.config.json` and `.github/workflows/audit.yaml` in the target repo, so that consumers no longer have to copy the canonical caller workflow by hand from this repo. The workflow content is shipped as a bundled template that ships to npm, and the repo's own workflow is kept byte-identical to that template via a consistency test — the canonical workflow cannot silently drift from what is published.",
+            "hash": "2b45c1047284e251fc48730104f971dcb88919d7"
+          },
+          {
+            "description": "Add migrate-tag-prefixes.sh migration tool (#282)",
+            "body": "Adds a one-shot migration tool, `migrate-tag-prefixes.sh`, shipped inside the release-kit package. The tool creates additive annotated-tag aliases under release-kit's new unscoped-package-name prefix that point at the same commits as the previous directory-basename tags, bridging the gap so post-migration `getCommitsSinceTarget` calls can resolve prior releases.",
+            "hash": "bd8f81f488db4e92aad16f59cb0ecc734bc22e8c"
+          },
+          {
+            "description": "Add legacyTagPrefixes config field (#289)",
+            "body": "Replaces the v4 → v5 tag-prefix migration mechanism (tag aliasing via `migrate-tag-prefixes.sh`) with a declarative `legacyTagPrefixes` config field. release-kit now searches for both legacy and modern prefixes when generating changelogs.\n\nAdds a companion `release-kit show-tag-prefixes` CLI command that renders a per-workspace table of derived and declared legacy prefixes, flags cross-workspace collisions, and surfaces undeclared candidate prefixes with a copy-pasteable config snippet. `release-kit prepare` gains a one-line hint pointing operators to `show-tag-prefixes` when a workspace has no baseline tag but the repo contains candidate-shaped tags.",
+            "breaking": true,
+            "hash": "c2425c53cfbe382ea91a653463ae41664d9e1c41"
+          },
+          {
+            "description": "Replace `legacyTagPrefixes` with `legacyIdentities` (#297)",
+            "body": "Replaces the per-workspace `legacyTagPrefixes: string[]` field with `legacyIdentities: LegacyIdentity[]`, a structured array of complete `(name, tagPrefix)` historical snapshots. Each legacy identity is now a self-consistent record of what a workspace used to be called and how its tags used to be prefixed, so a workspace that has been renamed (npm name change, tag-prefix change, or both) carries one entry per prior identity.",
+            "breaking": true,
+            "hash": "9b2a5ef01e6340f30f465c3c7bfc9e9c9db9f39e"
+          },
+          {
+            "description": "Add `retiredPackages` repo-level config field (#299)",
+            "body": "Adds support for declaring packages that once lived in this repo but have been extracted or removed, so their historical tag prefixes (e.g., `preflight-v*` from the extracted `readyup` project) no longer surface as \"Undeclared tag prefixes\" in `release-kit show-tag-prefixes`. Declared retired packages are acknowledged as real history but never consulted for baseline lookup or changelog attribution — they complement `workspaces[].legacyIdentities`, which is used when a workspace still exists under a new identity.",
+            "hash": "649974b1f72aff5a5ccba8204bc2a4cd6d39fcc3"
+          },
+          {
+            "description": "Add release-notes preview generator to `release-kit prepare` (#302)",
+            "body": "Adds the ability to generate release notes when running `release-kit prepare`. The `--with-release-notes` option enables the generation of per-workspace preview files so authors can verify release-note injection before publishing.  Injected release notes are also now prefixed with a `## Release notes — v{version} ({date})` heading to add missing context to the README.",
+            "hash": "988ab7ccaaad9eca598967342119ad5e4ba25e8e"
+          }
+        ]
+      },
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Derive monorepo tag prefix from unscoped `package.json` name (#278)",
+            "body": "Fixes a long-standing mismatch between a monorepo workspace's directory basename and its publishable package identity.",
+            "hash": "1f73fbeb7b928f9211d2b34ef6db30e4e696266d"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Rename `component` to `workspace` in config API and internals (#296)",
+            "body": "Renames release-kit's per-workspace vocabulary from \"component\" to \"workspace\" throughout the public API, internal types, validation messages, CLI help, init templates, and documentation. Behavior is unchanged; only identifiers, error-message strings, scaffolded template text, and prose have been changed.",
+            "breaking": true,
+            "hash": "dfe0a70903997b85a2ebf57a612345be5232a2c6"
+          },
+          {
+            "description": "Rename `node-monorepo-core` to `nmr-core` (#304)",
+            "body": "Renames the shared-utilities package from `@williamthorsen/node-monorepo-core` to `@williamthorsen/nmr-core`, aligning it with the repository's `nmr-*` naming convention. The package's functionality and version are unchanged; only the published name differs.",
+            "breaking": true,
+            "hash": "085d4a57d1828bcd33933652aa47423989c090a9"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "4.8.0",
+    "date": "2026-04-17",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Add `push` command for safe tag pushing (#243)",
+            "body": "Adds a `release-kit push` command that safely pushes the release commit and each tag individually, ensuring GitHub Actions fires a separate workflow run per tag. The command performs a `1 + N` push sequence: one branch push followed by one `git push --no-follow-tags origin <tag>` per resolved tag. Supports `--dry-run` (preview without pushing), `--only` (filter tags by package name), and `--tags-only` (skip the branch push).",
+            "hash": "5d92193d3a7bb37943cb232c25c6de8318b0be04"
+          }
+        ]
+      },
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Replace broad catch with `existsSync` guard in `detectRepoType` (#229)",
+            "body": "Fixes silent swallowing of unexpected filesystem errors in `detectRepoType`. Previously, errors like `EACCES` (permission denied) or `EMFILE` (too many open files) when reading `package.json` were caught and discarded, causing the function to silently return `'single-package'` instead of surfacing the problem.",
+            "hash": "36bc346a5a54726c1ebf9abb0bf0b4f3041d0bbb"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "4.7.0",
+    "date": "2026-04-16",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Support ## as synthetic ticket prefix in changelogs",
+            "body": "Commits prefixed with `##` are now included in changelogs without requiring a ticket ID. This supports ad-hoc changes made during interactive sessions where creating a ticket and PR adds undesired overhead.",
+            "hash": "88f4649a1d2a2d661b7be1273ca19b28893d0090"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "4.6.0",
+    "date": "2026-04-15",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Guard `prepare` against dirty working tree (#188)",
+            "body": "Add a clean-working-tree check at the start of `prepareCommand` that exits with an error when `git status --porcelain` reports uncommitted changes. This prevents the double-bump problem where running `prepare` multiple times bumps the version each time from the already-bumped `package.json`.\n\nThe check can be bypassed with `--no-git-checks` (`-n`) and is automatically skipped during `--dry-run`.",
+            "hash": "7a098258869a05c3e4ee8e63b5bdefe6b2e278ff"
+          },
+          {
+            "description": "Add sync-labels drift detection to release-kit readyup kit (#190)",
+            "body": "Adds readyup kit checks that detect when a consumer's sync-labels workflow or generated labels file has drifted from the current templates and presets. The `generate` command now embeds per-preset content hashes in the `labels.yaml` header, enabling hash-based staleness detection.",
+            "hash": "b7a14d39a6a9a53e29fd14a3b230e8285f1e3d85"
+          },
+          {
+            "description": "Improve changelog formatting & add cliff config drift detection (#193)",
+            "body": "Improves changelog generation: cleanly indented commit bodies, stripped type prefixes, and no unticketed noise. Adds hash-based drift detection so the rdy kit warns when a consumer's local cliff config falls behind the current template. Fixes a latent bug where git-cliff rejected the bundled `.template` file extension.",
+            "hash": "af78852cb1db6112b6a1be7adb029f7f60f52b15"
+          },
+          {
+            "description": "Generate release notes distinct from changelogs (#199)",
+            "body": "Adds structured changelog generation with audience tagging to the `release-kit` package, enabling GitHub Release creation and npm README injection with user-facing release notes filtered from developer-only sections. The existing CHANGELOG.md pipeline is unchanged; a new `.meta/changelog.json` artifact is generated in parallel during `release-kit prepare`, and consumed during `release-kit publish` to create GitHub Releases and inject release notes into the published package's README.",
+            "hash": "9bbcf4f434123404c2e6b014b858a953c1d62ed1"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Decouple GitHub Release creation and README injection from npm publish (#203)",
+            "body": "Makes GitHub Release creation available as a standalone CLI command (`release-kit github-release`) and removes README injection logic from the publish function. Non-published projects (applications, websites, internal tools) can now create GitHub Releases independently after `release-kit prepare`, and the inject/restore lifecycle is managed by the command layer rather than buried inside business logic.",
+            "hash": "5f09250c52a804023e12599f54a54c73628e482f"
+          }
+        ]
+      },
+      {
+        "title": "⚙️ Tooling",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Enable automated publication to npm (#187)",
+            "body": "Prepares the repository for reliable tag-triggered npm publishing by adding missing package metadata, standardizing licensing, and introducing a readyup kit that validates publish readiness across all packages.",
+            "hash": "89536cbcb5bb9aa30620bd262dce2c99f84ee0bc"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "4.5.1",
+    "date": "2026-04-10",
+    "sections": [
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Fix sync-labels init scaffolding output (#179)",
+            "body": "Fixes three issues in `release-kit sync-labels init` scaffolding output that cause immediate errors for consumers: adds missing workflow permissions, corrects config template indentation from 2 to 4 spaces, and switches YAML quoting from double to single quotes.",
+            "hash": "34526929b61a5dfce4630afaac0c69ede89dffc1"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "4.4.0",
+    "date": "2026-04-04",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Add --version flag to nmr and release-kit (#143)",
+            "body": "Adds `--version` / `-V` support to the `nmr` and `release-kit` CLIs, matching the existing `preflight` behavior. Moves the build-time version generation script to the shared `config/` directory so all three packages use a single `generateVersion.ts`.",
+            "hash": "7257a8eb37a622e0065f105d09f41541b76c7d8e"
+          },
+          {
+            "description": "Detect and report missing build output in bin wrappers (#152)",
+            "body": "Adds try/catch with `ERR_MODULE_NOT_FOUND` detection to all six bin wrappers across `nmr`, `preflight`, and `release-kit`. Previously, five of the six wrappers used bare `import()` calls that produced cryptic unhandled rejections when `dist/` was missing, and `preflight`'s existing try/catch gave no actionable guidance.",
+            "hash": "1e7bdbe21e66c61762286da695aeab7afa9ec115"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Extract deleteFileIfExists helper (#136)",
+            "body": "Replaces the duplicate `deleteTagsFile` and `deleteSummaryFile` functions in `createTags.ts` with a single parameterized `deleteFileIfExists(path)` utility. The new helper lives in its own module and is exported from the package barrel for reuse.",
+            "hash": "4f9e73f9b4ac1e54b898009ee3ea197a57911f18"
+          },
+          {
+            "description": "Extract shared CLI argument-parsing utility into core (#151)",
+            "body": "Add a schema-driven `parseArgs` function to `@williamthorsen/node-monorepo-core` that handles boolean flags, string flags (both `--flag=value` and `--flag value`), short aliases, positional collection, the `--` delimiter, and unknown-flag errors. Migrate all CLI argument-parsing sites in preflight (3 sites) and release-kit (5 sites) to use it. A companion `translateParseError` helper normalizes internal error messages for consistent user-facing output.",
+            "hash": "70d3523db108c7c5ea9d29be57dc14371f52581f"
+          }
+        ]
+      },
+      {
+        "title": "📚 Documentation",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Refine README to match preflight documentation standard (#138)",
+            "body": "Restructures the release-kit README to match the documentation standard established by the preflight README (#114). Reorders sections to follow the cross-package convention, converts CLI flag listings from code blocks to tables, adds representative `prepare --dry-run` output to the quick start, and condenses ~90 lines of inline workflow YAML into a summary with an inputs table and trigger examples. Fixes several accuracy gaps found by verifying documentation against source.",
+            "hash": "41b1765642e322158ed03ae1b44d4378f1979f02"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "4.0.0",
+    "date": "2026-04-02",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Rename reusable workflows to .reusable.yaml convention (#129)",
+            "body": "Renames all three reusable GitHub Actions workflow files from the inconsistent `-workflow.yaml`/bare `.yaml` convention to a uniform `.reusable.yaml` suffix. Updates all references across caller workflows, release-kit templates, tests, preflight collection, and documentation. Scaffolds the sync-labels caller workflow and labels file for this repo. Deletes superseded legacy files.",
+            "hash": "0085c902e052e1d82973d7a25e10375eee51c9d2"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "3.0.0",
+    "date": "2026-03-29",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Support conventional-commit format in commit parsing (#85)",
+            "body": "Adds support for the conventional commits format (`type(scope): description`) alongside the existing pipe-prefixed format (`scope|type: description`) in release-kit's commit parser. Renames `workspace` to `scope` throughout release-kit types, config, validation, and consumers.",
+            "breaking": true,
+            "hash": "a54dfa6a21b7d7ebe69ac83027c39a30916df1c7"
+          },
+          {
+            "description": "Add commit command for local release flow (#89)",
+            "body": "Adds a `release-kit commit` command that centralizes the release commit step between `prepare` and `tag`. The command reads tag names and a per-component commit summary from temporary files written by `prepare`, stages all changes, and creates a formatted commit. Two new utilities — `stripScope` and `buildReleaseSummary` — support building the commit body by stripping redundant scope indicators and formatting commits under their component headings. The CI workflow is simplified to use `release-kit commit` and `release-kit tag` instead of inline shell logic.",
+            "hash": "75fe4b968b41dc30c8b5eaa99fee3f34d9f3616a"
+          },
+          {
+            "description": "Add CI publish workflow with OIDC trusted publishing (#90)",
+            "body": "Adds automated npm publication via a tag-push-triggered GitHub Actions workflow using OIDC trusted publishing. Extends `release-kit publish` with a `--provenance` flag and `release-kit init` with publish workflow scaffolding.",
+            "hash": "bfa2b970d53124c49df6ae15648168680defb482"
+          },
+          {
+            "description": "Make --provenance opt-in to support private repos (#94)",
+            "body": "Adds a `provenance` boolean input (default `false`) to the reusable `publish-workflow.yaml` so private repos using OIDC trusted publishing no longer fail at publish time. The `--provenance` flag is only passed to `release-kit publish` when the caller sets `provenance: true`.\n\nUpdates the scaffolded `publish.yaml` template to include `provenance: false` with an inline comment guiding public repos to opt in. Expand the `release-kit init` next-steps output with hints about the provenance setting and trusted publisher registration. Set `provenance: true` in this repo's own `publish.yaml` since it is public.",
+            "hash": "833b08003e45b16ec16a2f07b28ac9fc5a7aeb7b"
+          }
+        ]
+      },
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Pass tag pattern to git-cliff based on tagPrefix (#77)",
+            "body": "Fixes the issue that git-cliff was processing the entire commit history on every run instead of only commits since the last release.\n\nConstructs the pattern from `tagPrefix` at invocation time (e.g., `release-kit-v` → `release-kit-v[0-9].*`) and pass it via `--tag-pattern`, which overrides the config file default.",
+            "hash": "724d1da533aad3cede69bb4eb0fc11682772e775"
+          },
+          {
+            "description": "Propagate version bumps to workspace dependents (#80)",
+            "body": "Restructures `releasePrepareMono` from a single-pass loop into a phased pipeline that automatically patch-bumps workspace dependents when a component is released. A reverse dependency graph is built from `workspace:` references in `dependencies` and `peerDependencies`, then BFS propagation walks upward from bumped components to their dependents. Propagated-only components receive synthetic changelog entries instead of git-cliff invocations.",
+            "hash": "859ff90abfe50dfbd32d8548c38876c3ecf1884e"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "2.3.2",
+    "date": "2026-03-28",
+    "sections": [
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Prevent unparseable commits from being silently dropped (#76)",
+            "body": "Prevents `releasePrepareMono` and `releasePrepare` from silently skipping components whose commits have unparseable messages. Adds ticket-prefix stripping to `parseCommitMessage` (mirroring cliff.toml's `commit_preprocessors`), a patch-floor safety net when commits exist but none parse, and unparseable-commit reporting in `reportPrepare`.",
+            "hash": "d737d37a2549a6e0e8cf25272ebfdce27521173d"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "2.3.0",
+    "date": "2026-03-28",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Add shared writeFileWithCheck utility and overwrite reporting (#66)",
+            "body": "Extracts three duplicated `writeIfAbsent` implementations and two duplicated terminal helper sets into shared utilities in `@williamthorsen/node-monorepo-core`, then migrates all consumers (`release-kit init`, `preflight init`, `sync-labels`) to use them. All init commands now report which files were created, overwritten, skipped, or failed — including when `--force` replaces existing files.",
+            "hash": "209f5e581cad267cf8365d8284c4fcf161faf177"
+          },
+          {
+            "description": "Separate tag-write errors from release preparation errors (#67)",
+            "body": "When tag-file writing fails, the error message now reads \"Error writing release tags:\" instead of the misleading \"Error preparing release:\", which only appeared because both operations shared a single try/catch.\n\nRefactors `writeReleaseTags` to use the shared `writeFileWithCheck` utility from `@node-monorepo-tools/core` instead of raw `mkdirSync`/`writeFileSync`. The function now returns a structured `WriteResult` instead of throwing, and contains no `console` calls — all presentation moves to `runAndReport`.",
+            "hash": "04c835d7d67d7f1fe8643738dbeb76813ec08766"
+          }
+        ]
+      },
+      {
+        "title": "🧪 Tests",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Add eligibility check failure and short-circuit tests (#63)",
+            "body": "Adds 4 unit tests to `initCommand.unit.test.ts` covering the remaining `checkEligibility` orchestration gaps: individual failure exit codes for `hasPackageJson` and `usesPnpm`, and short-circuit verification ensuring downstream checks are skipped when an earlier check fails.",
+            "hash": "9e0257f6965815cd2b3baa9c15b0044ae73a2498"
+          },
+          {
+            "description": "Add cliff.toml.template alignment test (#64)",
+            "body": "Adds a unit test that enforces bidirectional alignment between `DEFAULT_WORK_TYPES` and the bundled `cliff.toml.template` commit parsers. The test parses the TOML template using `smol-toml`, then verifies that every canonical type name and alias is matched by a parser with the correct group heading, and that every parser group maps to a known work type header.",
+            "hash": "e98ac307aa5dbb3a79fb98d84c259295907a0a1f"
+          },
+          {
+            "description": "Add releasePrepare coverage for bumpOverride, tagPrefix, and dry-run tags (#65)",
+            "body": "Adds three unit tests to `releasePrepare.unit.test.ts` covering previously untested code paths: the `bumpOverride` bypass of commit-based bump detection, custom `tagPrefix` propagation into tags, and tag computation in dry-run mode.",
+            "hash": "dd647e60f06581373408577a600d3b8b7aa609d6"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "2.2.0",
+    "date": "2026-03-27",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Add sync-labels command (#33)",
+            "body": "Add a `release-kit sync-labels` command group with three subcommands (`init`, `generate`, `sync`) for declarative GitHub label management in monorepos. Bundle a reusable GitHub Actions workflow and composable label presets with the release-kit package. Introduce a `findPackageRoot` utility to replace fragile hardcoded path resolutions across the codebase.",
+            "hash": "4345a41b1f85570be483d31f5406f689be673241"
+          },
+          {
+            "description": "Report up-to-date status for unchanged init files (#35)",
+            "body": "`release-kit init` now compares existing file content against the default before reporting status. When an existing file is identical to the default (after normalizing trailing whitespace), it reports `✅ (up to date)` instead of the misleading `⚠️ (already exists)`.",
+            "hash": "0402702f055c021dd57819219403c8fbea693a8a"
+          },
+          {
+            "description": "Auto-detect Prettier for CHANGELOG formatting (#36)",
+            "body": "When `formatCommand` is not configured, release-kit now auto-detects whether the repo uses Prettier by checking for config files (`.prettierrc*`, `prettier.config.*`) or a `\"prettier\"` key in root `package.json`. If found, it defaults to `npx prettier --write` on generated files. If not found, formatting is skipped.",
+            "hash": "97432b9d68068cfa2b40c9e9246afc92026c33ec"
+          },
+          {
+            "description": "Add tag-creation command (#40)",
+            "body": "Adds a `release-kit tag` CLI command that reads computed tag names from the `tmp/.release-tags` file produced by `prepare` and creates annotated git tags. The command supports `--dry-run` (preview without creating tags) and `--no-git-checks` (skip dirty working tree validation). The `createTags` function and its options type are exported for programmatic use.",
+            "hash": "a8a7d4f5c9e80d8c7e3eb2b237881882470e2361"
+          },
+          {
+            "description": "Add publish command (#42)",
+            "body": "Adds a `release-kit publish` subcommand that derives packages to publish from git tags on HEAD and delegates to the repo's detected package manager. Also cleans up the `.release-tags` file after tag creation.",
+            "hash": "c452a464d8ebf5eaf90d89a332a62f514e792378"
+          },
+          {
+            "description": "Remove tagPrefix customization from component config (#49)",
+            "body": "Removes the ability to customize `tagPrefix` per component, enforcing the deterministic `{dir}-v` convention universally. The internal `tagPrefix` property on `ComponentConfig` and `ReleaseConfig` is preserved — only the override/customization entry points are removed. Existing configs that still include `tagPrefix` now receive a clear deprecation error.",
+            "hash": "c19976ab40d412bef2315a9322dbf7606aebc90f"
+          },
+          {
+            "description": "Add styled terminal output to prepare command (#55)",
+            "body": "Adds ANSI formatting and emoji markers to the `release-kit prepare` command output. Progress chatter is dimmed, key results (version bumps, release tags, completion status) are highlighted with bold text and emoji, and monorepo components are separated by box-drawing section headers.",
+            "hash": "fb18fe6f0acd94fe3a9b929c90139c75e5d9205b"
+          },
+          {
+            "description": "Extract nmr CLI from core package (#61)",
+            "body": "Extracts all nmr CLI code from `packages/core` into a new `packages/nmr` package (`@williamthorsen/nmr`). Core is reduced to an empty shared-library shell ready for cross-cutting utilities. All internal references are rewired and the full build/test pipeline passes.\n\nScopes: core, nmr",
+            "hash": "d1abff0286f593a24444c0113d0286b4e70d6973"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Replace dist bin targets with thin wrapper scripts (#48)",
+            "body": "The `bin` entries in `packages/core` and `packages/release-kit` pointed directly into `dist/esm/`, causing `pnpm install` to emit \"Failed to create bin\" warnings in fresh worktrees where `dist/` does not yet exist. Each bin entry now points to a committed wrapper script in `bin/` that dynamically imports the real entry point. The `files` field in both packages includes `bin` so the wrappers are published.",
+            "hash": "7cbc147a270d860fea7f3166032fb71a36b6522d"
+          },
+          {
+            "description": "Separate presentation from logic in prepare workflow (#57)",
+            "body": "Extracts all `console.info` calls from the prepare workflow's logic functions (`bumpAllVersions`, `generateChangelogs`, `releasePrepare`, `releasePrepareMono`) into a dedicated `reportPrepare` formatter. Logic functions now return structured result types (`BumpResult`, `ComponentPrepareResult`, `PrepareResult`). The legacy `runReleasePrepare` entry point is retired, with its utilities absorbed into `prepareCommand`.",
+            "hash": "c929a7f618f0cae57af2028c27643b49cf931e14"
+          }
+        ]
+      },
+      {
+        "title": "🧪 Tests",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Cover multi-changelogPaths and error paths (#44)",
+            "body": "Add three tests for previously untested code paths:\n\n- `releasePrepareMono`: component with two `changelogPaths` entries, asserting `git-cliff` is invoked once per path with the correct `--output` target.\n- `getCommitsSinceTarget`: `git describe` failure with a non-128 exit status propagates as a wrapped error instead of being swallowed.\n- `getCommitsSinceTarget`: `git log` failure is wrapped and re-thrown with the commit range in the message.\n\nAlso adds a `findAllCliffOutputPaths()` test helper that collects the `--output` arg from every `git-cliff` mock call.",
+            "hash": "f5513c3b17acd8b53a81011ac63a937ef34abb07"
+          }
+        ]
+      },
+      {
+        "title": "⚙️ Tooling",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Adopt nmr to run monorepo and workspace scripts (#38)",
+            "body": "Replaces the legacy workspace script runner and ~25 root `package.json` scripts with `nmr`, the monorepo's own context-aware script runner. Root scripts are reduced to 4 (`prepare`, `postinstall`, `ci`, `bootstrap`), packages use direct build commands for bootstrap, and release-kit declares tier-3 test overrides for its integration test configs.",
+            "hash": "4a0b6fbc877c31daaf9472af3b9df948f6d19a12"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "2.1.0",
+    "date": "2026-03-17",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Migrate release-kit from toolbelt (#18)",
+            "body": "Migrates the complete `@williamthorsen/release-kit` package (v1.0.1) from `williamthorsen/toolbelt` into `packages/release-kit/`, adds shebang preservation to the shared esbuild plugin for CLI binaries, and sets up dogfooding infrastructure so this monorepo uses release-kit for its own releases.",
+            "hash": "da3a61fd335fb3e05ce20a0bffcdc1647d7aeb45"
+          },
+          {
+            "description": "Slim down release workflow by removing unnecessary pnpm install (#21)",
+            "body": "Make release-kit self-contained by invoking git-cliff via `npx --yes` instead of requiring it on PATH, and by appending modified file paths to the format command so lightweight formatters like `npx prettier --write` work without a full `pnpm install`. Update init templates, README, and consuming repo config/workflow to reference workflow v3.",
+            "breaking": true,
+            "hash": "996258dc895dd98704da253e51a5f0975ac5cf42"
+          },
+          {
+            "description": "Add --force flag to release-kit prepare (#25)",
+            "body": "Add a `--force` flag to `release-kit prepare` that bypasses the \"no commits since last tag\" check in monorepo mode, allowing version bumping and changelog generation to proceed even when no new commits are found since the last release tag. The flag requires `--bump` since there are no commits to infer bump type from. The local release workflow gains a `force` boolean input for future use.",
+            "hash": "79940296abf5476e077585d7681265ecf01cf8e4"
+          },
+          {
+            "description": "Move reusable release workflow into repo (#26)",
+            "body": "Moves the reusable release workflow from `williamthorsen/.github` into this repo as `release-workflow.yaml`, stripping all pnpm-related steps since release-kit now runs git-cliff and prettier via `npx` internally. Updates this repo's caller workflow to use a relative path and update init templates to reference the new location. Establishes a naming convention (`{name}-workflow.yaml` for reusable, `{name}.yaml` for callers) and independent versioning strategy (`{name}-workflow-v{major}` tags), documented in `.github/workflows/README.md`.",
+            "breaking": true,
+            "hash": "f3416120cfe5bf0e7dbf51389e0c2647ccf41d30"
+          },
+          {
+            "description": "Allow git-cliff to be used without config (#31)",
+            "body": "Adds a `resolveCliffConfigPath()` function that searches for a git-cliff config in a 4-step cascade (explicit path → `.config/git-cliff.toml` → `cliff.toml` → bundled `cliff.toml.template`), eliminating the requirement for consuming repos to maintain a cliff config copy. Restructures the `init` command to scaffold only the workflow file by default, with new `--with-config` and `--force` flags. Moves `.release-tags` from `/tmp/release-kit/` to project-local `tmp/` for predictable behavior in local runs.",
+            "hash": "0cbd2605d6f5f53d1efe3dda8dd0f6e4376b499f"
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Clean up release-kit post-migration issues (#19)",
+            "body": "Addresses five code quality issues and a test coverage gap identified during the release-kit migration (#5). Extracts a duplicated `isRecord` type guard into a shared module, eliminates a double-read in `bumpAllVersions`, improves error handling in `usesPnpm` by replacing a silent catch with a structured error boundary, removes an unreachable `'feature'` pattern from version defaults, and adds an integration test for scaffold template path resolution.",
+            "hash": "aa50ca62ffb8fa0e7f727cf15794d4ba5ed2cf0e"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "1.0.1",
+    "date": "2026-03-14",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Migrate release-kit from toolbelt (#18)",
+            "body": "Migrates the complete `@williamthorsen/release-kit` package (v1.0.1) from `williamthorsen/toolbelt` into `packages/release-kit/`, adds shebang preservation to the shared esbuild plugin for CLI binaries, and sets up dogfooding infrastructure so this monorepo uses release-kit for its own releases.",
+            "hash": "da3a61fd335fb3e05ce20a0bffcdc1647d7aeb45"
+          }
+        ]
+      }
+    ]
+  }
+]