chore: remove .rhiza/.cfg.toml - #507
Conversation
Drop the bump-my-version configuration. No Makefile target or GitHub workflow references this path; releasing is driven by the rhiza-claude /release command, which is the remaining consumer to verify. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThe pull request deletes Changes
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Removes the Rhiza-local bump-my-version configuration file (.rhiza/.cfg.toml) from the repository, presumably to retire that version-bumping mechanism in favor of the Rhiza-driven release flow.
Changes:
- Delete
.rhiza/.cfg.toml(thebump-my-versionconfig).
Suppressed comments (1)
.rhiza/.cfg.toml:1
- This file is still listed as template-managed in
.rhiza/template.lockand.rhiza/history(both reference.rhiza/.cfg.toml). Removing it here will likely be reverted by the next Rhiza sync/update, and it leaves the template metadata inconsistent with the working tree. Either keep this file until the upstream template/lock is updated, or update the Rhiza metadata (lock/history and/or exclude rules) in the same PR so the deletion persists.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Removes
.rhiza/.cfg.toml, thebump-my-versionconfiguration.Notes
.rhiza/make.d/*.mk,Makefile,.github/workflows/)..rhiza/make.d/releasing.mkstates version bumping is not a make target and that releasing is driven by the rhiza-claude/releasecommand — that command is the remaining potential consumer and is worth verifying before merge.make fmtpasses on this branch (all pre-commit hooks green).🤖 Generated with Claude Code
Summary by CodeRabbit