Migrate from discontinued bump2version to bump-my-version

docs/development/tools/release.md

@@ -6,10 +6,10 @@ Currently, GT4Py releases are published in PyPI (and TestPyPI) and also as commi
 
 1. Make sure all the expected changes (new features, bug fixes, documentation changes, etc.) are already included in the `main` public branch.
 
-2. Use **bump2version** to update the version number.
+2. Use **bump-my-version** to update the version number.
 
    ```bash
-   $ bump2version minor # or patch
+   $ bump-my-version bump minor # or patch
    ```
 
 3. Update the [CHANGELOG.md](CHANGELOG.md) file to document the changes included in the new release. Note that this step becomes much simpler when commit messages follow the [Conventional Commits][conventional-commits] convention as encouraged in the [Pull Request and Merge Guidelines](CONTRIBUTING.md#pull-request-and-merge-guidelines) section of the contributing guidelines.

pyproject.toml

@@ -94,6 +94,27 @@ Homepage = 'https://gridtools.github.io/'
 Source = 'https://github.com/GridTools/gt4py'
 
 # ---- Other tools ----
+# -- bump-my-version --
+[tool.bumpversion]
+allow_dirty = false
+commit = false
+commit_args = ''
+current_version = '1.0.3'
+ignore_missing_version = false
+message = 'Bump version: {current_version} → {new_version}'
+parse = '(?P<major>\d+)\.(?P<minor>\d+)(\.(?P<patch>\d+))?'
+regex = false
+replace = '{new_version}'
+search = '{current_version}'
+serialize = ['{major}.{minor}.{patch}']
+sign_tags = false
+tag = false
+tag_message = 'Bump version: {current_version} → {new_version}'
+tag_name = 'v{new_version}'
+
+[[tool.bumpversion.files]]
+filename = "src/gt4py/__about__.py"
+
 # -- coverage --
 [tool.coverage]
 

requirements-dev.in

@@ -5,6 +5,7 @@
 # should be added here without constraints, so they will use the
 # constraints defined in `pyproject.toml`.
 #
+bump-my-version>=0.19.3
 clang-format>=9.0
 cogapp>=3.3
 coverage[toml]>=5.0