ship

# Ship Release Systematic release workflow for RTK: build verification, version bump, changelog update, git tag, and push to trigger CI/CD. ## When to Use - **Manual invocation**: When ready to release a new version - **After feature completion**: Before tagging and publishing - **Before version bump**: To automate the release checklist ## Pre-Release Checklist (Auto-Verified) Before running `/ship`, verify: ### 1. Quality Checks Pass ```bash cargo fmt --all --check # Code formatted cargo clippy --all-targets # Zero warnings cargo test --all # All tests pass ``` ### 2. Performance Benchmarks Pass ```bash hyperfine 'target/release/rtk git status' --warmup 3 # Should show <10ms mean time /usr/bin/time -l target/release/rtk git status # Should show <5MB maximum resident set size ``` ### 3. Integration Tests Pass ```bash cargo install --path . --force # Install locally cargo test --ignored # Run integration tests ``` ### 4. Git Clean State ```bash git status # Should show "nothing to commit, working tree clean" ``` ## Release Workflow ### Step 1: Determine Version Bump **Semantic Versioning** (MAJOR.MINOR.PATCH): - **MAJOR** (v1.0.0): Breaking changes (rare for RTK) - **MINOR** (v0.X.0): New features, new filters, new commands - **PATCH** (v0.0.X): Bug fixes, performance improvements **Examples**: - New filter added (`rtk pytest`) → **MINOR** bump (v0.16.0 → v0.17.0) - Bug fix in `git log` filter → **PATCH** bump (v0.16.0 → v0.16.1) - Break...