mirror of
https://github.com/RooVetGit/Roo-Code.git
synced 2026-09-07 08:26:51 +00:00
6214f4c162
* Roo Code CLI v0.0.50 * docs(cli): add --exit-on-error to changelog --------- Co-authored-by: Roo Code <roomote@roocode.com>
86 lines
2.4 KiB
Markdown
86 lines
2.4 KiB
Markdown
---
|
|
description: "Prepare a new release of the Roo Code CLI"
|
|
argument-hint: "[version-description]"
|
|
mode: code
|
|
---
|
|
|
|
1. 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`
|
|
|
|
2. 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
|
|
|
|
3. 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
|
|
|
|
4. Update `apps/cli/CHANGELOG.md` with a new entry:
|
|
|
|
- Add a new section at the top (below the header) following this format:
|
|
|
|
```markdown
|
|
## [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
|
|
|
|
5. Create a release branch and commit the changes:
|
|
|
|
```bash
|
|
# 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>
|
|
```
|
|
|
|
6. Create a pull request for the release:
|
|
|
|
```bash
|
|
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
|
|
```
|