cli-release

Identify changes since the last CLI release:

• Get the last CLI release tag: gh release list --limit 10 | grep "cli-v"
• View changes since last release: git log cli-v<last-version>..HEAD -- apps/cli --oneline
• Or for uncommitted changes: git diff --stat -- apps/cli

Review and summarize the changes to determine an appropriate changelog entry. Group changes by type:

• Added: New features
• Changed: Changes to existing functionality
• Fixed: Bug fixes
• Removed: Removed features
• Tests: New or updated tests

Bump the version in apps/cli/package.json:

• Increment the patch version (e.g., 0.0.43 → 0.0.44) for bug fixes and minor changes
• Increment the minor version (e.g., 0.0.43 → 0.1.0) for new features
• Increment the major version (e.g., 0.0.43 → 1.0.0) for breaking changes

Update apps/cli/CHANGELOG.md with a new entry:

• Add a new section at the top (below the header) following this format:

## [X.Y.Z] - YYYY-MM-DD

### Added

- Description of new features

### Changed

- Description of changes

### Fixed

- Description of bug fixes

• Use the current date in YYYY-MM-DD format
• Include links to relevant source files where helpful
• Describe changes from the user's perspective

Create a release branch and commit the changes:

# Ensure you're on main and up to date
git checkout main
git pull origin main

# Create a new branch for the release
git checkout -b cli-release-v<version>

# Commit the version bump and changelog update
git add apps/cli/package.json apps/cli/CHANGELOG.md
git commit -m "chore(cli): prepare release v<version>"

# Push the branch to origin
git push -u origin cli-release-v<version>

Create a pull request for the release:

gh pr create --title "chore(cli): prepare release v<version>" \
    --body "## CLI Release v<version>

This PR prepares the CLI release v<version>.

### Changes
- Version bump in package.json
- Changelog update

### Checklist
- [ ] Version number is correct
- [ ] Changelog entry is complete and accurate
- [ ] All CI checks pass" \
    --base main