gtbump
git tag bump: A simple utility to bump and manage semver git tags and generate Markdown changelogs.
Install
pip install gtbump
Usage
# cd to your git repo.
# see the last tag.
$ gtbump --show
no tags found. Run --init to add v0.1.0
# add a tag for the first time.
$ gtbump --init
bumped v0.0.0 -> v0.1.0
# bump major | minor | patch
$ gtbump --minor
bumped v0.1.0 -> v0.2.0
$ gtbump --major
bumped v0.2.0 -> v1.2.0
# delete the last tag
$ gtbump --delete-last
deleted v1.2.0
# push the last tag upstream(or --push-last=your_remote_name)
$ gtbump --push-last
pushing v0.3.0 to origin
# generate changelog for the latest tag. This can be copy-pasted into GitHub's release description.
$ gtbump --changelog
changelog for v1.0.0 -> v1.1.0
- b361292 Display app version the settings UI
- a3b285f Fix Buefy number input width
- 63520d2 Merge pull request #388 from dunklesToast/chore/update-german-translations
- 3abac31 chore(translations): improve german translations
- 3ecac76 Fix Vue linting issue
Check gtbump --help for more options.
Licensed under the MIT license.
1 maintainer
Metadata
1 maintainer
Release files for gtbump 1.2.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 | |
|---|---|---|---|---|
| gtbump-1.2.1.tar.gz | 4.3 kB | Without provenance | Details |
Release files / gtbump-1.2.1.tar.gz
| Download URL | gtbump-1.2.1.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
41910305cbe1fc501712d191ab15b0757d5fe06313f2c4812ba4d519ae569f83
|
|
BLAKE2b-256 checksum How to use checksums |
3120392c9618c4ee3962dda9797915f5c0e81ca8a66d46f4daf463d4ea85bb6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.24.0 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.9
|
Security for gtbump 1.2.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.
