Migrate from deprecated bump2version to bump-my-version

[Copilot]

Migration from deprecated bump2version to bump-my-version (rebased on master):

• Replace bump2version dependency with bump-my-version in pyproject.toml
• Update release.py CLI commands from bumpversion --list to bump-my-version bump --verbose
• Add new parsing function for bump-my-version verbose output format
• Update tests to reflect new command name and output format
• Rebase on master (31 commits ahead)
• Resolve merge conflicts with master branch
• All tests passing (11/11 release tests pass)

Summary

Successfully migrated from deprecated bump2version to bump-my-version and rebased on latest master. The new implementation uses --verbose flag to extract version information from command output. All conflicts have been resolved and tests are passing.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>bump2version deprecated: use bump-my-version</issue_title>
<issue_description>https://github.com/c4urself/bump2version/blob/master/README.md</issue_description>

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

• Fixes bump2version deprecated: use bump-my-version #139

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[ivantodorovich]

@copilot can you resolve conflicts?

[Copilot]

@copilot can you resolve conflicts?

Conflicts resolved in commit f3ffe0a. The branch has been rebased onto master and all tests are passing (11/11 release tests pass).

Key changes:

• Resolved conflicts in odoo_tools/cli/release.py and tests/test_release.py
• Updated to use --verbose flag for both dry-run and normal bump commands
• The version is now extracted from verbose output using the pattern "New version will be 'X.Y.Z'"

Note: The branch will need to be force-pushed since it has been rebased.

[simahawk]

@copilot rebase and solve conflicts please

[Copilot]

@copilot rebase and solve conflicts please

Rebase completed in commit f88079e. The branch has been rebased onto latest master (31 commits ahead) and all tests are passing (11/11 release tests pass).

Changes:

• Resolved conflicts in odoo_tools/cli/release.py and tests/test_release.py
• Integrated master's updates while maintaining migration to bump-my-version
• Uses bump-my-version bump --verbose for all runs
• Version extraction from "New version will be 'X.Y.Z'" pattern

The branch needs to be force-pushed since it has been rebased.

[simahawk]

I don't think this is reliable...

[ivantodorovich]

This is only for the dry-run. Is that even useful, given we always work in a git repo?

Either we remove --dry-run support and forget about parsing the version from the output.

Or we keep it but by simply running --dry-run with verbose=True and relay the exact output of bump-my-version to the user, instead of a fancy "New version: (parsed_version)"