Changelog

This project uses a single latest-docs strategy.

• Docs always describe the current released CLI behavior.
• Version is displayed globally in docs and synced from the root package version.

Current Version

See the version label in the docs footer.

Release Notes Process

1. Update CLI behavior and tests.
2. Update relevant docs pages in the same change.
3. Add a release note with pnpm changeset:add (bump level plus a description for people installing the package) and commit it with the change.
4. To release, a maintainer runs pnpm changeset:prepare-release in a release pull request. It bumps the root package version, writes the entry into CHANGELOG.md, and syncs the version shown in these docs.
5. Merging the release pull request publishes the package, tags it, and creates the GitHub release from the changelog entry. The docs deploy on their own when docs/ changes.

Historical Changes

From 2.1.0 on, release notes are written to CHANGELOG.md and to the GitHub releases page . Earlier releases are tracked in Git history and pull requests.