Automatically bump version when merging to master.
## Status
| Travis CI (Ubuntu) | Coverage | PyPI | Licence |
|--------------------|----------|------|---------|
|[](http://travis-ci.org/polysquare/travis-bump-version)|[](http://coveralls.io/polysquare/travis-bump-version)|[](https://pypi.python.org/pypi/travis-bump-version)[](https://pypi.python.org/pypi/travis-bump-version)|[](http://github.com/polysquare/travis-bump-version)|
## Usage
usage: travis-bump-version [-h] --api-token API_TOKEN --repo REPO
[FILE [FILE ...]]
Automatically bump version on successful Travis-CI builds.
positional arguments:
FILE bump version on FILE
optional arguments:
-h, --help show this help message and exit
--api-token API_TOKEN
GitHub API token. Always make sure this variable is
encrypted first.
--repo REPO Name of repo on GitHub, eg user/repo.
On Travis-CI you can use the `TRAVIS_REPO_SLUG` variable to determine
the current repository. See [this guide](https://github.com/blog/1509-personal-api-tokens)
on how to generate an API token. Remember to encrypt it first using
`travis encrypt --add env.global` first!
1 maintainer
Metadata
1 maintainer
Release files for travis-bump-version 0.1.12
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 |
|---|---|---|---|---|
| travis-bump-version-0.1.12.tar.gz | 5.2 kB | Without provenance | Details for travis-bump-version-0.1.12.tar.gz |
Release files / travis-bump-version-0.1.12.tar.gz
| Download URL | travis-bump-version-0.1.12.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6747380f1203a89ab0375d893ef63da1f4de46f935ca9121b6d058d68cbe01e6
|
|
BLAKE2b-256 checksum How to use checksums |
6ff18b0f40dda698c5ce559e4b1d603c883046a46f9b9adfdf07917c380f9c42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for travis-bump-version 0.1.12
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.
