feat: pass --config through release to bump command

[Copilot]

release --with-bump (and --bump) would fail if the bumpversion config file wasn't at the default .rhiza/.cfg.toml path — the --config option accepted by bump had no equivalent on release and was never forwarded internally.

Changes

• cli.py — Added --config / -c option to the release command, reusing the shared CONFIG_OPTION already defined for bump; passes it through to release_command()
• release.py — Added config: Path | None = None to release_command() and _perform_version_bump(); forwards the path into BumpOptions when bump_command is called internally
• Tests — Updated existing mock-call assertions to include the new config arg; added a test case verifying --config is forwarded correctly to release_command

Usage

# Config file at a non-default path
rhiza-tools release --with-bump --config /custom/path/.cfg.toml
rhiza-tools release --bump MINOR --push --config /custom/path/.cfg.toml

Original prompt

---

This section details on the original issue you should resolve

<issue_title>release --with-bump should allow config file path to be passed to the bump command</issue_title>
<issue_description>### Description

release --with-bump all fail if .cfg.toml Is not in .rhiza

Steps to reproduce

move .cfg.toml and rhiza-tools release --with-bump --config ..

Expected behaviour

you should be able to passthrough the same options via release

Environment

No response

Additional context

No response</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes release --with-bump should allow config file path to be passed to the bump command #158

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.