move to bump-my-version #24
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bb98909dd6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| abort "Please provide valid revision: #{AVAILABLE_REVISIONS.join(',')}" | ||
| end | ||
|
|
||
| system "bumpversion #{args.revision}" | ||
| system "bump-my-version bump #{args.revision}" |
There was a problem hiding this comment.
The bump task now executes bump-my-version bump ..., but it still depends on :has_bumpversion, which only checks for the legacy bumpversion executable. On a system where only the new bump-my-version CLI is installed (the expected setup after this commit), rake bump/rake release will abort before running because the preflight reports the old binary missing. Align the preflight check with the new command so releases can run.
Useful? React with 👍 / 👎.
No description provided.