{{ define "main" }} {{ $p := .Site.Params }}
THE PYTHON VERSION TOOLKIT

One version.
Everywhere.

Find version declarations across your project. Check that they agree. Preview the next bump before anything changes.

INSTALLpipx install jiggle_version
PROJECT VERSION MAP IN SYNC
v2.2.1ONE SOURCE OF TRUTH
01pyproject.toml2.2.1
02setup.cfg2.2.1
03__version__.py2.2.1
DISCOVER WITHOUT IMPORTING/CHECK WITHOUT WRITING/BUMP WITH INTENT
01 — A CONTROLLED SEQUENCE

Know what’s there.
Then move it forward.

Version values can hide in build metadata and Python files. jiggle_version reads common declaration forms, verifies agreement, and makes an explicit change when you ask for one.

01SCAN

Discover

Find version declarations in pyproject.toml, setup.cfg, static setup.py, and Python modules.

jiggle_version inspect
02VERIFY

Check agreement

Catch drift in CI or locally with a read-only command. Optionally compare the result with the nearest Git tag.

jiggle_version check
03PREVIEW

Plan the bump

Choose a PEP 440 or SemVer increment. Dry-run mode shows the result without writing files.

jiggle_version bump --dry-run
02 — TRY THE READ-ONLY PATH

Start with
a quick check.

The default workflow keeps Git operations off. Run a check, inspect the agreed version, and preview the next patch.

Explore the CLI ↗
terminal / project-root
$ jiggle_version check
# Verify that discovered sources agree
$ jiggle_version print
# Print the agreed version
$ jiggle_version bump --increment patch --dry-run
# Preview changes without writing
03 — BUILT FOR REAL PROJECTS

Precise where
it matters.

01

No target import

Reads Python declarations with AST parsing, so a check does not execute your package.

02

Two version schemes

Choose PEP 440 or SemVer for major, minor, and patch increments.

03

Git actions are opt-in

Staging, committing, and pushing are separate autogit choices; the default is off.

READY WHEN YOUR PROJECT IS

Keep the next release
in step.

pipx install jiggle_versionRead the documentation ↗
{{ end }}