poetry-bumpversion
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.
Getting Started
Prerequisites
poetry = ^1.2.0a2
Install
Install the plugin by poetry plugin command.
poetry self add poetry-bumpversion
Configure version replacements
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.
Advanced Usage
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}'
License
This project is licensed under MIT License - see the LICENSE file for details.
Metadata
Release files for poetry-bumpversion 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| poetry-bumpversion-0.3.0.tar.gz | 6.1 kB | Without provenance | Details for poetry-bumpversion-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| poetry_bumpversion-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for poetry_bumpversion-0.3.0-py3-none-any.whl |
Total release size: 12.2 kB
Release files / poetry-bumpversion-0.3.0.tar.gz
| Download URL | poetry-bumpversion-0.3.0.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aeff169c5bfa93d6c8542ba06b0545e02db91252a65d25317cd5c7e10d91dfd6
|
|
BLAKE2b-256 checksum How to use checksums |
1f316381ce6ba139c687aa1846ad63352e3f1908b0a2c1a2418073e1feea6a68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.1 CPython/3.8.10 Linux/5.15.0-1020-azure
|
Release files / poetry_bumpversion-0.3.0-py3-none-any.whl
| Download URL | poetry_bumpversion-0.3.0-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
57dbfa4c986f55e97769f95967495559cb99e58a7ee587a1ecb3cd81d1f93464
|
|
BLAKE2b-256 checksum How to use checksums |
83503021545f6824987a542839e243f9e67b6e15b5ca219a0cee4f5f9705aa01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.1 CPython/3.8.10 Linux/5.15.0-1020-azure
|
Security for poetry-bumpversion 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.