@williamthorsen/release-kit 2.3.2 → 4.4.0

package/CHANGELOG.md

@@ -2,6 +2,76 @@
 
 All notable changes to this project will be documented in this file.
 
+## [release-kit-v4.4.0] - 2026-04-04
+
+### Documentation
+
+- #135 release-kit|docs: Refine README to match preflight documentation standard (#138)
+
+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.
+
+### Features
+
+- #142 feat: Add --version flag to nmr and release-kit (#143)
+
+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`.
+
+- #150 feat: Detect and report missing build output in bin wrappers (#152)
+
+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.
+
+### Refactoring
+
+- #88 release-kit|refactor: Extract deleteFileIfExists helper (#136)
+
+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.
+
+- #145 refactor: Extract shared CLI argument-parsing utility into core (#151)
+
+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.
+
+## [release-kit-v4.0.0] - 2026-04-02
+
+### Features
+
+- #125 feat: Rename reusable workflows to .reusable.yaml convention (#129)
+
+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.
+
+## [release-kit-v3.0.0] - 2026-03-29
+
+### Bug fixes
+
+- #68 release-kit|fix: Pass tag pattern to git-cliff based on tagPrefix (#77)
+
+Fixes the issue that git-cliff was processing the entire commit history on every run instead of only commits since the last release.
+
+Constructs 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.
+
+- #72 release-kit|fix: Propagate version bumps to workspace dependents (#80)
+
+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.
+
+### Features
+
+- #73 release-kit|feat!: Support conventional-commit format in commit parsing (#85)
+
+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.
+
+- #70 release-kit|feat: Add commit command for local release flow (#89)
+
+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.
+
+- #69 release-kit|feat: Add CI publish workflow with OIDC trusted publishing (#90)
+
+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.
+
+- #91 release-kit|feat: Make --provenance opt-in to support private repos (#94)
+
+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`.
+
+Updates 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.
+
 ## [release-kit-v2.3.2] - 2026-03-28
 
 ### Bug fixes
@@ -40,8 +110,28 @@ Adds three unit tests to `releasePrepare.unit.test.ts` covering previously untes
 
 ## [release-kit-v2.2.0] - 2026-03-27
 
+### Dependencies
+
+- Root|deps: Add release-kit as root devDependency
+
+Make `npx release-kit` and `pnpm exec release-kit` resolve within
+this repo by adding a `workspace:*` dependency that symlinks the bin.
+
 ### Features
 
+- #23 release-kit|feat: Add sync-labels command (#33)
+
+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.
+
+- #34 release-kit|feat: Report up-to-date status for unchanged init files (#35)
+
+`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)`.
+
+- Release-workflow|feat: Accept force input
+
+Pass `--force` to the prepare command so callers can force a version
+bump even when there are no release-worthy changes.
+
 - #27 release-kit|feat: Auto-detect Prettier for CHANGELOG formatting (#36)
 
 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.
@@ -96,30 +186,6 @@ Also adds a `findAllCliffOutputPaths()` test helper that collects the `--output`
 
 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.
 
-## [release-workflow-v1] - 2026-03-19
-
-### Dependencies
-
-- Root|deps: Add release-kit as root devDependency
-
-Make `npx release-kit` and `pnpm exec release-kit` resolve within
-this repo by adding a `workspace:*` dependency that symlinks the bin.
-
-### Features
-
-- #23 release-kit|feat: Add sync-labels command (#33)
-
-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.
-
-- #34 release-kit|feat: Report up-to-date status for unchanged init files (#35)
-
-`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)`.
-
-- Release-workflow|feat: Accept force input
-
-Pass `--force` to the prepare command so callers can force a version
-bump even when there are no release-worthy changes.
-
 ## [release-kit-v2.1.0] - 2026-03-17
 
 ### Features

package/README.md

@@ -20,6 +20,36 @@ npx @williamthorsen/release-kit init
 npx @williamthorsen/release-kit prepare --dry-run
 ```
 
+Example output from `prepare --dry-run` in a monorepo:
+
+```
+🔍 DRY RUN — no files will be modified
+
+── arrays ──────────────────────────────────────
+  Found 4 commits since arrays-v1.2.0
+  Parsed 3 typed commits
+  Bumping versions (minor)...
+  📦 1.2.0 → 1.3.0 (minor)
+  [dry-run] Would bump packages/arrays/package.json
+  Generating changelogs...
+  [dry-run] Would run: npx --yes git-cliff ... --output packages/arrays/CHANGELOG.md
+  🏷️  arrays-v1.3.0
+
+── strings ─────────────────────────────────────
+  Found 2 commits since strings-v0.5.1
+  Parsed 2 typed commits
+  Bumping versions (patch)...
+  📦 0.5.1 → 0.5.2 (patch)
+  [dry-run] Would bump packages/strings/package.json
+  Generating changelogs...
+  [dry-run] Would run: npx --yes git-cliff ... --output packages/strings/CHANGELOG.md
+  🏷️  strings-v0.5.2
+
+✅ Release preparation complete.
+   🏷️  arrays-v1.3.0
+   🏷️  strings-v0.5.2
+```
+
 That's it for most repos. The CLI auto-discovers workspaces and applies sensible defaults. The bundled `cliff.toml.template` is used automatically — no need to copy it. Customize only what you need via `.config/release-kit.config.ts`.
 
 ## How it works
@@ -30,43 +60,20 @@ That's it for most repos. The CLI auto-discovers workspaces and applies sensible
 4. **Version bump + changelog**: bumps `package.json` versions and generates changelogs via `git-cliff`.
 5. **Release tags file**: writes computed tags to `tmp/.release-tags` for the release workflow to read when tagging and pushing.
 
-## CLI reference
-
-### `release-kit prepare`
-
-Run release preparation with automatic workspace discovery.
+## Commit format
 
-```
-Usage: release-kit prepare [options]
+release-kit parses commits in these formats:
 
-Options:
-  --dry-run                   Preview changes without writing files
-  --bump=major|minor|patch    Override the bump type for all components
-  --only=name1,name2          Only process the named components (monorepo only)
-  --help, -h                  Show help
 ```
-
-Component names for `--only` match the package directory name (e.g., `arrays`, `release-kit`).
-
-### `release-kit init`
-
-Initialize release-kit in the current repository. By default, scaffolds only the GitHub Actions workflow file. Use `--with-config` to also scaffold configuration files.
-
+type: description              # e.g., feat: add utility
+scope|type: description        # e.g., arrays|feat: add compact function
+type(scope): description       # e.g., feat(arrays): add compact function
+type!: description             # breaking change (triggers major bump)
+scope|type!: description       # scoped breaking change
+type(scope)!: description      # conventional scoped breaking change
 ```
-Usage: release-kit init [options]
 
-Options:
-  --with-config    Also scaffold .config/release-kit.config.ts and .config/git-cliff.toml
-  --force          Overwrite existing files instead of skipping them
-  --dry-run        Preview changes without writing files
-  --help, -h       Show help
-```
-
-Scaffolded files:
-
-- `.github/workflows/release.yaml` — workflow that delegates to a reusable release workflow
-- `.config/release-kit.config.ts` — starter config with commented-out customization examples (with `--with-config`)
-- `.config/git-cliff.toml` — copied from the bundled template (with `--with-config`)
+The `scope|type:` format scopes a commit to a specific component in a monorepo. Use `scopeAliases` in your config to map shorthand names to canonical scope names.
 
 ## Configuration
 
@@ -98,14 +105,14 @@ The config file supports both `export default config` and `export const config =
 
 ### `ReleaseKitConfig` reference
 
-| Field              | Type                             | Description                                                                                                                   |
-| ------------------ | -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| `cliffConfigPath`  | `string`                         | Explicit path to cliff config. If omitted, resolved automatically: `.config/git-cliff.toml` → `cliff.toml` → bundled template |
-| `components`       | `ComponentOverride[]`            | Override or exclude discovered components (matched by `dir`)                                                                  |
-| `formatCommand`    | `string`                         | Shell command to run after changelog generation; modified file paths are appended as arguments                                |
-| `versionPatterns`  | `VersionPatterns`                | Rules for which commit types trigger major/minor bumps                                                                        |
-| `workspaceAliases` | `Record<string, string>`         | Maps shorthand workspace names to canonical names in commits                                                                  |
-| `workTypes`        | `Record<string, WorkTypeConfig>` | Work type definitions, merged with defaults by key                                                                            |
+| Field             | Type                             | Description                                                                                                                   |
+| ----------------- | -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| `cliffConfigPath` | `string`                         | Explicit path to cliff config. If omitted, resolved automatically: `.config/git-cliff.toml` → `cliff.toml` → bundled template |
+| `components`      | `ComponentOverride[]`            | Override or exclude discovered components (matched by `dir`)                                                                  |
+| `formatCommand`   | `string`                         | Shell command to run after changelog generation; modified file paths are appended as arguments                                |
+| `versionPatterns` | `VersionPatterns`                | Rules for which commit types trigger major/minor bumps                                                                        |
+| `scopeAliases`    | `Record<string, string>`         | Maps shorthand scope names to canonical names in commits                                                                      |
+| `workTypes`       | `Record<string, WorkTypeConfig>` | Work type definitions, merged with defaults by key                                                                            |
 
 All fields are optional.
 
@@ -129,7 +136,7 @@ interface VersionPatterns {
 }
 ```
 
-Default: `{ major: ['!'], minor: ['feat', 'feature'] }`
+Default: `{ major: ['!'], minor: ['feat'] }`
 
 ### Default work types
 
@@ -148,149 +155,70 @@ Default: `{ major: ['!'], minor: ['feat', 'feature'] }`
 
 Work types from your config are merged with these defaults by key — your entries override or extend, they don't replace the full set.
 
-## Commit format
+## CLI reference
 
-release-kit parses commits in these formats:
+### Global options
 
-```
-type: description              # e.g., feat: add utility
-type(scope): description       # e.g., fix(parser): handle edge case
-workspace|type: description    # e.g., arrays|feat: add compact function
-!type: description             # breaking change (triggers major bump)
-```
+| Flag              | Description         |
+| ----------------- | ------------------- |
+| `--help`, `-h`    | Show help message   |
+| `--version`, `-V` | Show version number |
 
-The `workspace|type:` format scopes a commit to a specific workspace in a monorepo. Use `workspaceAliases` in your config to map shorthand names to canonical workspace names.
+### `release-kit prepare`
 
-## Using `component()` for manual configuration
+Run release preparation with automatic workspace discovery.
 
-If you need to build a `MonorepoReleaseConfig` manually (e.g., for the legacy script-based approach), the exported `component()` helper creates a `ComponentConfig` from a workspace-relative path:
+| Flag                         | Description                                                      |
+| ---------------------------- | ---------------------------------------------------------------- |
+| `--dry-run`                  | Preview changes without writing files                            |
+| `--bump=major\|minor\|patch` | Override the bump type for all components                        |
+| `--force`                    | Bypass the "no commits since last tag" check (requires `--bump`) |
+| `--only=name1,name2`         | Only process the named components (monorepo only)                |
+| `--help`, `-h`               | Show help                                                        |
 
-```typescript
-import { component } from '@williamthorsen/release-kit';
+Component names for `--only` match the package directory name (e.g., `arrays`, `release-kit`).
 
-// Accepts the full workspace-relative path
-component('packages/arrays');
-// => {
-//   dir: 'arrays',
-//   tagPrefix: 'arrays-v',
-//   packageFiles: ['packages/arrays/package.json'],
-//   changelogPaths: ['packages/arrays'],
-//   paths: ['packages/arrays/**'],
-// }
-```
+### `release-kit init`
 
-The `dir` field is derived from `path.basename()`, so `packages/arrays` and `libs/arrays` both produce `dir: 'arrays'`. The `tagPrefix` is always `${dir}-v` — it cannot be customized.
+Initialize release-kit in the current repository. By default, scaffolds only the GitHub Actions workflow file. Use `--with-config` to also scaffold configuration files.
 
-## GitHub Actions workflow
+| Flag            | Description                                                                |
+| --------------- | -------------------------------------------------------------------------- |
+| `--with-config` | Also scaffold `.config/release-kit.config.ts` and `.config/git-cliff.toml` |
+| `--force`       | Overwrite existing files instead of skipping them                          |
+| `--dry-run`     | Preview changes without writing files                                      |
+| `--help`, `-h`  | Show help                                                                  |
 
-The `init` command scaffolds a workflow that delegates to a reusable release workflow. For repos that need a self-contained workflow:
-
-### Monorepo
-
-```yaml
-name: Release
-
-on:
-  workflow_dispatch:
-    inputs:
-      only:
-        description: 'Components to release (comma-separated, leave empty for all)'
-        required: false
-        type: string
-      bump:
-        description: 'Override bump type (leave empty to auto-detect)'
-        required: false
-        type: choice
-        options:
-          - ''
-          - patch
-          - minor
-          - major
-
-permissions:
-  contents: write
-
-jobs:
-  release:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          token: ${{ secrets.GITHUB_TOKEN }}
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: '24'
-
-      - name: Run release preparation
-        run: |
-          ARGS=""
-          if [ -n "${{ inputs.only }}" ]; then
-            ARGS="$ARGS --only=${{ inputs.only }}"
-          fi
-          if [ -n "${{ inputs.bump }}" ]; then
-            ARGS="$ARGS --bump=${{ inputs.bump }}"
-          fi
-          npx @williamthorsen/release-kit prepare $ARGS
-
-      - name: Check for changes
-        id: check
-        run: |
-          if git diff --quiet; then
-            echo "changed=false" >> "$GITHUB_OUTPUT"
-            echo "No release-worthy changes found."
-          else
-            echo "changed=true" >> "$GITHUB_OUTPUT"
-          fi
-
-      - name: Read release tags
-        if: steps.check.outputs.changed == 'true'
-        id: tags
-        run: |
-          TAGS=$(cat tmp/.release-tags | tr '\n' ' ')
-          echo "tags=$TAGS" >> "$GITHUB_OUTPUT"
-          echo "Releasing: $TAGS"
-
-      - name: Commit, tag, and push
-        if: steps.check.outputs.changed == 'true'
-        run: |
-          git config user.name "github-actions[bot]"
-          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
-          git add -A
-          git commit -m "release: ${{ steps.tags.outputs.tags }}"
-          for TAG in ${{ steps.tags.outputs.tags }}; do
-            git tag "$TAG"
-          done
-          git push origin main ${{ steps.tags.outputs.tags }}
-```
+Scaffolded files:
 
-### Single-package repo
+- `.github/workflows/release.yaml` — workflow that delegates to a reusable release workflow
+- `.config/release-kit.config.ts` — starter config with commented-out customization examples (with `--with-config`)
+- `.config/git-cliff.toml` — copied from the bundled template (with `--with-config`)
 
-The same workflow without the `only` input. Replace the prepare step with:
+### `release-kit sync-labels`
 
-```yaml
-- name: Run release preparation
-  run: |
-    ARGS=""
-    if [ -n "${{ inputs.bump }}" ]; then
-      ARGS="--bump=${{ inputs.bump }}"
-    fi
-    npx @williamthorsen/release-kit prepare $ARGS
-```
+Manage GitHub label definitions via config-driven YAML files.
 
-And the tag step with:
+| Subcommand | Description                                                    | Flags                  |
+| ---------- | -------------------------------------------------------------- | ---------------------- |
+| `init`     | Scaffold config, caller workflow, and generate labels          | `--dry-run`, `--force` |
+| `generate` | Regenerate `.github/labels.yaml` from config                   | —                      |
+| `sync`     | Trigger the `sync-labels` GitHub Actions workflow via `gh` CLI | —                      |
 
-```yaml
-- name: Read release tag
-  if: steps.check.outputs.changed == 'true'
-  id: tags
-  run: |
-    TAG=$(cat tmp/.release-tags)
-    echo "tag=$TAG" >> "$GITHUB_OUTPUT"
-```
+`init` scaffolds `.config/sync-labels.config.ts` with auto-detected workspace scope labels and a `.github/workflows/sync-labels.yaml` caller workflow, then generates `.github/labels.yaml`. `generate` reads the config and writes `.github/labels.yaml`. `sync` triggers the workflow remotely — it requires the `gh` CLI and an existing workflow file.
+
+## GitHub Actions workflow
+
+The `init` command scaffolds a release workflow at `.github/workflows/release.yaml` that delegates to a reusable release workflow. The scaffolded workflow accepts these inputs:
+
+| Input  | Type   | Description                                                         |
+| ------ | ------ | ------------------------------------------------------------------- |
+| `only` | string | Components to release (comma-separated, leave empty for all)        |
+| `bump` | choice | Override bump type: `patch`, `minor`, `major` (empty = auto-detect) |
 
-## Triggering a release
+For repos that need a self-contained workflow instead of the reusable one, the scaffolded file can be expanded. The key steps are: checkout with full history (`fetch-depth: 0`), run `release-kit prepare` with optional `--only` and `--bump` flags, check for changes, read tags from `tmp/.release-tags`, then commit, tag, and push.
+
+### Triggering a release
 
 ```sh
 # All components
@@ -305,12 +233,14 @@ Or use the GitHub UI: Actions > Release > Run workflow.
 
 ## cliff.toml setup
 
-The package includes a bundled `cliff.toml.template` that is used automatically when no custom config is found. The resolution order is:
+The package includes a bundled `cliff.toml.template` that is used automatically when no custom config is found. The resolution order:
 
-1. Explicit `cliffConfigPath` in `.config/release-kit.config.ts`
-2. `.config/git-cliff.toml`
-3. `cliff.toml` (repo root)
-4. Bundled `cliff.toml.template` (automatic fallback)
+| Priority | Path                          | Notes                                           |
+| -------- | ----------------------------- | ----------------------------------------------- |
+| 1        | `cliffConfigPath` in config   | Explicit path, returned without existence check |
+| 2        | `.config/git-cliff.toml`      | Project-level override                          |
+| 3        | `cliff.toml`                  | Repo root fallback                              |
+| 4        | Bundled `cliff.toml.template` | Automatic fallback                              |
 
 The bundled template provides a generic git-cliff configuration that:
 
@@ -327,6 +257,26 @@ This package shells out to two external tools:
 - **`git`** — must be available on `PATH`. Used to find tags and retrieve commit history.
 - **`git-cliff`** — automatically downloaded and cached via `npx` on first invocation. No need to install it as a dev dependency.
 
+## Using `component()` for manual configuration
+
+If you need to build a `MonorepoReleaseConfig` manually (e.g., for the legacy script-based approach), the exported `component()` helper creates a `ComponentConfig` from a workspace-relative path:
+
+```typescript
+import { component } from '@williamthorsen/release-kit';
+
+// Accepts the full workspace-relative path
+component('packages/arrays');
+// => {
+//   dir: 'arrays',
+//   tagPrefix: 'arrays-v',
+//   packageFiles: ['packages/arrays/package.json'],
+//   changelogPaths: ['packages/arrays'],
+//   paths: ['packages/arrays/**'],
+// }
+```
+
+The `dir` field is derived from `path.basename()`, so `packages/arrays` and `libs/arrays` both produce `dir: 'arrays'`. The `tagPrefix` is always `${dir}-v` — it cannot be customized.
+
 ## Legacy script-based approach
 
 The CLI-driven approach is recommended for new setups. The script-based approach (using `runReleasePrepare` with a manually maintained config) is still supported for backward compatibility.

package/bin/release-kit.js

@@ -1,2 +1,11 @@
 #!/usr/bin/env node
-import('../dist/esm/bin/release-kit.js');
+try {
+  await import('../dist/esm/bin/release-kit.js');
+} catch (error) {
+  if (error.code === 'ERR_MODULE_NOT_FOUND') {
+    process.stderr.write('release-kit: build output not found — run `pnpm run build` first\n');
+  } else {
+    process.stderr.write(`release-kit: failed to load: ${error.message}\n`);
+  }
+  process.exit(1);
+}

package/cliff.toml.template

@@ -45,19 +45,20 @@ commit_preprocessors = [
   { pattern = '^[A-Z]+-\d+\s+', replace = "" },
 ]
 # regex for parsing and grouping commits
-# Supports both "type: description" and "workspace|type: description" formats
+# Supports "type: desc", "scope|type: desc", and "type(scope): desc" formats
 commit_parsers = [
-  { message = "^.*\\|?fix(!)?:", group = "Bug fixes" },
-  { message = "^.*\\|?feat(!)?:", group = "Features" },
-  { message = "^.*\\|?feature(!)?:", group = "Features" },
-  { message = "^.*\\|?internal(!)?:", group = "Internal" },
-  { message = "^.*\\|?refactor(!)?:", group = "Refactoring" },
-  { message = "^.*\\|?tests?(!)?:", group = "Tests" },
-  { message = "^.*\\|?tooling(!)?:", group = "Tooling" },
-  { message = "^.*\\|?ci(!)?:", group = "CI" },
-  { message = "^.*\\|?deps?(!)?:", group = "Dependencies" },
-  { message = "^.*\\|?docs?(!)?:", group = "Documentation" },
-  { message = "^.*\\|?fmt(!)?:", group = "Formatting" },
+  { message = "^(.*\\|)?fix(\\(.*\\))?(!)?:", group = "Bug fixes" },
+  { message = "^(.*\\|)?bugfix(\\(.*\\))?(!)?:", group = "Bug fixes" },
+  { message = "^(.*\\|)?feat(\\(.*\\))?(!)?:", group = "Features" },
+  { message = "^(.*\\|)?feature(\\(.*\\))?(!)?:", group = "Features" },
+  { message = "^(.*\\|)?internal(\\(.*\\))?(!)?:", group = "Internal" },
+  { message = "^(.*\\|)?refactor(\\(.*\\))?(!)?:", group = "Refactoring" },
+  { message = "^(.*\\|)?tests?(\\(.*\\))?(!)?:", group = "Tests" },
+  { message = "^(.*\\|)?tooling(\\(.*\\))?(!)?:", group = "Tooling" },
+  { message = "^(.*\\|)?ci(\\(.*\\))?(!)?:", group = "CI" },
+  { message = "^(.*\\|)?deps?(\\(.*\\))?(!)?:", group = "Dependencies" },
+  { message = "^(.*\\|)?docs?(\\(.*\\))?(!)?:", group = "Documentation" },
+  { message = "^(.*\\|)?fmt(\\(.*\\))?(!)?:", group = "Formatting" },
 ]
 # protect breaking changes from being skipped due to matching a skipping commit_parser
 protect_breaking_commits = false

package/dist/esm/.cache

@@ -1 +1 @@
-894421aa6cf2eb13518310f0bb75d5751a6a68ae1fcb068600b25ed30eea9b67
+89fa3a396cfa2f4f2cf5ce8827dbe171e310519ab3faa7325268a87693116335