dover v0.5.1
A commandline utility for incrementing your project version numbers.
Installation
... pip install dover
What does it do?
When dover is run from the root directory of your project, it does the following:
looks for a configuration file (.dover, .dover.ini, setup.cfg, pyproject.toml)
reads any dover configuration line in this format:
[dover:file:relatvie/file.pth]Or in the case of pyproject.toml:
[tool.dover] versioned_files = ["pyproject.toml", "dover/cli.py"]
searches the configured file references for “version” strings
validates all version strings across all configured files.
displays and/or increments the version strings based upon cli options.
Usage
... dover --help
dover v0.5.1
dover is a commandline utility for
tracking and incrementing your
project version numbers.
Usage:
dover [--list] [--debug] [--format=<fmt>]
dover increment ((--major|--minor|--patch)
[--dev|--alpha|--beta|--rc] |
[--major|--minor|--patch]
(--dev|--alpha|--beta|--rc) | --release)
[--apply] [--debug] [--no-list] [--format=<fmt>]
Options:
-M --major Update major version segment.
-m --minor Update minor version segment.
-p --patch Update patch version segment.
-d --dev Update dev version segment.
-a --alpha Update alpha pre-release segment.
-b --beta Update beta pre-release segment.
-r --rc Update release candidate segment.
-R --release Clear pre-release version.
-x --no-list Do not list files.
--format=<fmt> Apply format string.
--debug Print full exception info.
-h --help Display this help message
--version Display dover version.
See Read The Docs for more.
History
0.5.0 (2018-11-25)
added new dover config option for projects using pyproject.toml
started use of black for code formating
0.4.0 (2018-03-10)
Added –dev option as a pre-release state.
Added –release option that clears any pre-release versioning.
Added –format option that allows user to control the format from the standard 0.0.0-dev.1 format.
0.3.1 (2018-03-02)
documentation update to deal with invalid README formating.
0.3.0 (2018-03-02)
added pre-release options
added –no-list option
expanded documentation
100% code coverage
0.2.1 (2018-02-22)
expanded tests
general code clean up
0.2.0 (2018-02-22)
improved alignment of output
added additional version matching check
0.1.0 (2018-02-18)
initial commit
Metadata
Release files for dover 0.5.1
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 |
|---|---|---|---|---|
| dover-0.5.1.tar.gz | 17.1 kB | Without provenance | Details for dover-0.5.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dover-0.5.1-py3-none-any.whl | Python 3 | none | any | Details for dover-0.5.1-py3-none-any.whl |
Total release size: 31.0 kB
Release files / dover-0.5.1.tar.gz
| Download URL | dover-0.5.1.tar.gz |
|---|---|
| Size | 17.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8236310e4418e1a9837f4e641084e51ec63ff246b716af23cf2c413214d02ffe
|
|
BLAKE2b-256 checksum How to use checksums |
bc80ced72c6415d6db4a45ada8773dbb38f711e84362eb6b317b5d77875a98b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.9.1 pkginfo/1.4.1 requests/2.18.4 setuptools/38.5.1 requests-toolbelt/0.8.0 tqdm/4.19.5 CPython/3.6.2
|
Release files / dover-0.5.1-py3-none-any.whl
| Download URL | dover-0.5.1-py3-none-any.whl |
|---|---|
| Size | 13.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f2ff62ff25569584f78383bafcb2dc561ec11bbf9c9e0e525ea90b497d931a46
|
|
BLAKE2b-256 checksum How to use checksums |
108f8eaadf77d8b4e6d2cfd33e8c6c5dc9e101de42bfa7e963057abde455bc9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.9.1 pkginfo/1.4.1 requests/2.18.4 setuptools/38.5.1 requests-toolbelt/0.8.0 tqdm/4.19.5 CPython/3.6.2
|
Security for dover 0.5.1
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.