Hunk uses Changesets for release-note fragments and npm version preparation.

For user-visible changes, add a changeset instead of editing CHANGELOG.md directly:

bun run changeset

Select hunkdiff and choose the semver bump that matches the shipped CLI/package change:

• patch for fixes and small behavior changes
• minor for new user-facing features
• major for breaking changes

The private root workspace lists packages/*, and Changesets discovers the published hunkdiff package at packages/hunk/package.json. Private implementation workspaces remain ignored and are never published.

For maintenance-only PRs that should not appear in release notes, create an empty changeset:

bun run changeset -- --empty

Release prep runs:

bun run release:version

CHANGELOG.md at the repository root is the canonical changelog consumed by the website and release tooling. The version wrapper temporarily stages that history beside the package for Changesets, then copies the generated release entry back to the root and removes the temporary package changelog. It also bumps packages/hunk/package.json for the release commit.

After the tag release publishes npm packages and GitHub release assets, verify Homebrew through Homebrew/homebrew-core. Hunk is on Homebrew's Autobump list, so do not open manual simple version-bump PRs. Wait for the automated hunk <version> PR, confirm it merges, then verify brew install hunk resolves to the released version. Use brew bump-formula-pr hunk --version <version> only if Homebrew maintainers ask for a manual bump or Autobump stalls unexpectedly.