bump-release

A release-cutting workflow that bumps versions, writes changelogs, and creates commits and annotated tags, supporting single-package repositories and workspace monorepos across regular releases, beta prereleases, and dry runs. It is invoked as a user command with optional package selectors, an explicit semver version (single-package only), and --beta or --dry-run flags.

Work begins with a bundled, read-only planner (scripts/plan-release.mjs) that emits one JSON fact base used as the source of truth: package discovery, previous tags and tag patterns, scoped changed, included, and excluded file lists, dependency edges, whether package selection is needed, and dirty-tree status. In pnpm workspaces it uses pnpm list when available and otherwise falls back to workspace-glob discovery, including negative patterns; Bun and npm-style workspaces use glob discovery. A clean working tree is required before any edits.

The workflow then resolves target packages, rejects an explicit version applied to more than one package, plans each version by Semantic Versioning (or the documented beta and prerelease transitions), and skips no-op releases with no relevant changes. Dependency cascade uses the planner's edges to update dependent ranges and pull affected packages into the plan, treating range widening as patch and peer-dependency majors as major unless the user confirms otherwise. Changelog entries follow the Common Changelog reference, ordered Changed, Added, Removed, Fixed, with present-tense imperative verbs and production-impacting changes only, so tests, CI, and dev tooling are excluded and beta releases skip the changelog. After a single formatting pass, packages are committed and tagged in dependency order using commit and tag patterns inferred from existing tags.