version-upper
Primarily a reaction to bumpversion not supporting git hashes -- issue
Overview
Usage: version-upper [OPTIONS] COMMAND [ARGS]...
A tool to update version strings in files using semantic versioning and
commit hashes.
Examples:
# bump commit hash version
version-upper bump commit_hash
# bump patch version
version-upper bump patch
# bump patch version as release candidate
version-upper bump patch --release-candidate
# bump minor version
version-upper bump minor
# bump major version
version-upper bump major
The config file adheres to the Config Pydantic schema, and is named
version-upper.json by default.
Here is a sample config:
{
"current_version": "0.0.0",
"current_semantic_version": "0.0.0",
"files": []
}
Options:
--config TEXT [default: version-upper.json]
--help Show this message and exit.
Commands:
bump Bumps version strings, updates config.
config-schema Prints the config schema in JSON
current-semantic-version Prints the current semantic version
current-version Prints the current version
release Removes rc from the version strings
sample-config Prints a sample config
Configuration
Create a file called version-upper.json (can be overridden using --config) like below:
{
"current_version": "0.0.0",
"current_semantic_version": "0.0.0",
"files": ["main.py", "app/version.json"]
}
Be sure to add files to "files" otherwise nothing will be updated :)
Metadata
Release files for version-upper 0.2.2
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 | |
|---|---|---|---|---|
| version-upper-0.2.2.tar.gz | 5.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| version_upper-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.7 kB
Release files / version-upper-0.2.2.tar.gz
| Download URL | version-upper-0.2.2.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b839b8d8dc6748b241603c57e27569d9bd2a1f53d7f1263fb3a4ae6a28e81aa7
|
|
BLAKE2b-256 checksum How to use checksums |
e7fb5e064fa83db7dc95179fa9ca66e510d3c18ed1f3e36b600f8a7e01b1071c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/47.1.0 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.8.5
|
Release files / version_upper-0.2.2-py3-none-any.whl
| Download URL | version_upper-0.2.2-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
001998b4977889ed7b5a2a1f7aa2d40eb8fe2820163891b13660e94e09239481
|
|
BLAKE2b-256 checksum How to use checksums |
36a684531ad99664a739f6fb79b66344bfeb935a562a8c7a3e8099ecc7e69f4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/47.1.0 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.8.5
|
Security for version-upper 0.2.2
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.