| name | release |
| description | Use when releasing a new Ravi CLI version — version bump, tagging, and verification |
Release Ravi CLI
Guide the release process for a new CLI version. This is a checklist — the user drives each step.
Arguments
The user should specify the version to release (e.g., "release 0.4.0").
Pre-Release Checklist
1. Verify clean state
git status
git log --oneline -5
2. Run full test suite
make test
make lint
3. Verify build works
make build API_URL=https://ravi.id
./bin/ravi version
4. Check CHANGELOG-worthy commits since last tag
git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-decorate
Review for any breaking changes that need documentation.
Release Steps
5. Create and push the version tag
git tag v<VERSION>
git push origin v<VERSION>
6. Monitor the release workflow
gh run list --limit 1
gh run watch
The workflow automatically:
- Runs tests
- Cross-compiles for darwin/amd64, darwin/arm64, linux/amd64, linux/arm64
- Creates tar.gz archives with SHA256 checksums
- Creates GitHub Release with auto-generated notes
- Updates the Homebrew formula in
ravi-hq/homebrew-tap
7. Verify the release
gh release view v<VERSION>
Confirm:
- All 4 platform archives are attached
- checksums.txt is present
- Release notes look correct
8. Verify Homebrew tap updated
gh api repos/ravi-hq/homebrew-tap/commits --jq '.[0].commit.message'
Should show: ravi <VERSION>
Rollback
If something goes wrong:
git tag -d v<VERSION>
git push origin :refs/tags/v<VERSION>
gh release delete v<VERSION> --yes
Platform Matrix
| OS | Arch | Binary Name |
|---|
| macOS | arm64 | ravi-darwin-arm64 |
| macOS | amd64 | ravi-darwin-amd64 |
| Linux | arm64 | ravi-linux-arm64 |
| Linux | amd64 | ravi-linux-amd64 |
Note: Windows (amd64) is built by the Makefile but NOT included in the release workflow.