The poetry version
command only updates version in pyproject.toml
file.
This plugin updates version in other files when poetry version <version>
command is executed.
- python = ^3.8
- poetry = ^1.2.0
Install the plugin by poetry plugin command.
poetry self add poetry-bumpversion
Say you have __version__
variable set at your_package/__init__.py
file
__version__ = "0.1.0" # It MUST match the version in pyproject.toml file
Add the following to your pyproject.toml
file.
[tool.poetry_bumpversion.file."your_package/__init__.py"]
# Duplicate the line above to add more files
Now run poetry version patch --dry-run
, if your output looks somewhat like below
you are all set (dry-run does not update any file).
Bumping version from 0.5.0 to 0.5.1 poetry-bumpversion: processed file: your_package/__init__.py
If dry-run output looks fine you can run version update command without dry-run flag to
check if version in both pyproject.toml
and your_package/__init__.py
file has been updated.
You can define search and replace terms to be more precise
[tool.poetry_bumpversion.file."your_package/__init__.py"]
search = '__version__ = "{current_version}"'
replace = '__version__ = "{new_version}"'
You can define replacements if you have same search/replace patterns across multiple files.
[[tool.poetry_bumpversion.replacements]]
files = ["your_package/__init__.py", "your_package/version.py"]
search = '__version__ = "{current_version}"'
replace = '__version__ = "{new_version}"'
[[tool.poetry_bumpversion.replacements]]
files = ["README.md"]
search = 'version: {current_version}'
replace = 'version: {new_version}'
This plugin can be used to bump version automatically during publishing to PyPI using a GitHub workflow.
When a release tag is created the workflow will use that tag name e.g 2.0.1
to update versions in every
files, build the package and publish to PyPI. This is how this plugin is deployed to PyPI.
To get started you can copy the deploy workflow code from this repo to your repo and set it up.
This project is licensed under MIT License - see the LICENSE file for details.