git-version-sync
A command-line tool to synchronize semantic versions between Git tags and pyproject.toml.
Links: Repository · PyPI · Issues
Features
- Check version status and consistency between Git tags and
pyproject.toml - Sync version discrepancies with flexible sync directions
- Bump versions following semantic versioning (major, minor, patch)
- Push commits and tags to remote repository
- Undo version bumps with optional remote cleanup
- GitHub Release integration for automated release creation
- Dry-run mode to preview changes before execution
- Custom annotations for Git tags
- Force mode for bypassing version mismatches
Installation
Requirements
- Python >= 3.11
- Git
Via PyPI (Recommended)
pip install git-version-sync
Or with pipx for isolated installation:
pipx install git-version-sync
From Source
git clone https://github.com/Finsa-SC/git-version-sync.git
cd git-version-sync
pip install -e .
Usage
Check Command
Verify version consistency between Git tags and pyproject.toml:
git-version-sync check
Options:
--no-fetch- Skip fetching tags from remote repository
Sync Command
Synchronize versions when discrepancies are detected:
git-version-sync sync
Options (mutually exclusive):
--to-git- Forcepyproject.tomlversion to match the highest Git tag--to-config- Force Git tag to matchpyproject.tomlversion
Bump Command
Increment the version in pyproject.toml and create a corresponding Git tag:
git-version-sync bump {major|minor|patch}
Options:
-f, --force- Force bump even if version mismatch occurs-p, --push- Automatically push commit and tag to remote-m, --message MESSAGE- Custom annotation message for the Git tag-r, --release [NOTES]- Create a GitHub release for the bumped version-d, --draft- Save the GitHub release as a draft (requires--release)-n, --dry-run- Perform a dry run without making any actual changes
Push Command
Push the active branch and Git tags to remote repository:
git-version-sync push
Arguments:
tags- Specific tag(s) to push (e.g.,v1.0.0 v1.0.1). If empty, pushes active version tag.
Options:
-a, --all- Push all local tags to remote
Undo Command
Undo/rollback the last version bump and delete its corresponding Git tag:
git-version-sync undo
Arguments:
target- Specific tag/version to undo (e.g.,v1.6.0). Default: latest tag.
Options:
-r, --remote- Also delete the target tag from remote repository-f, --force- Bypass confirmation prompts
Examples
Check current version status
$ git-version-sync check
Version is synchronized with highest local tag (v1.8.1)
Check without fetching from remote
$ git-version-sync check --no-fetch
Version is synchronized with highest local tag (v1.8.1)
Bump patch version
$ git-version-sync bump patch
Success bump version to v1.7.1
Bump minor version with custom message
$ git-version-sync bump minor -m "Add new features"
Success bump version to v1.8.0
Bump patch version with push and GitHub release
$ git-version-sync bump patch -p -r "Bug fixes and improvements"
Success bump version to v1.7.1
Pushing commit and tag to remote...
Created GitHub Release v1.7.1
Bump major version as draft release
$ git-version-sync bump major -p -r -d
Success bump version to v2.0.0
Pushing commit and tag to remote...
Created GitHub Release v2.0.0 (draft)
Dry-run preview before bumping
$ git-version-sync bump minor -m "Release" -p --dry-run
Updated pyproject.toml to v1.9.0 (DRY RUN)
Committed changes: 'bump version to v1.9.0' (DRY RUN)
Created Git tag v1.9.0 (DRY RUN)
Pushed commit and tag to remote (DRY RUN)
Success bump version to v1.9.0 (DRY RUN - no changes made)
Push to remote
$ git-version-sync push
Pushing branch and tags to remote...
Push specific tags
$ git-version-sync push v1.8.1 v1.8.0
Pushing specified tags to remote...
Push all local tags
$ git-version-sync push -a
Pushing all local tags to remote...
Undo latest version bump
$ git-version-sync undo
Are you sure you want to undo v1.8.0? (y/n): y
Successfully undone version bump
Undo specific version and delete from remote
$ git-version-sync undo v1.8.1 -r -f
Successfully undone v1.8.1 and deleted from remote
Display version
$ git-version-sync --version
git-version-sync 1.7.0
Dependencies
packaging>=26.3- For version parsing and comparison
License
See LICENSE file for details.
Author
Finsa-SC
Release files for git-version-sync 1.9.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 | |
|---|---|---|---|
| git_version_sync-1.9.0.tar.gz | 13.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| git_version_sync-1.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.1 kB
Release files / git_version_sync-1.9.0.tar.gz
| Download URL | git_version_sync-1.9.0.tar.gz |
|---|---|
| Size | 13.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2d9239261e9db01de6a339f295fc44bf95a715e470b7f57016c20dc035e203d
|
|
BLAKE2b-256 checksum How to use checksums |
6e364ee82a2a93436ad5288c680512b41aac08ff8799679c9b6c9bddca1a65b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.
Transparency logRelease files / git_version_sync-1.9.0-py3-none-any.whl
| Download URL | git_version_sync-1.9.0-py3-none-any.whl |
|---|---|
| Size | 22.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
853c4e6fc64a4fe032be75b960c6006de1802307c105c447f7dd084f133f12f7
|
|
BLAKE2b-256 checksum How to use checksums |
a31d4534242bd719fa48a16ab33f6ec41bcc82957a0950011b6d4b2c43f12f0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.
Transparency log