bump
Bumps package version numbers
Decision gist · record as of 2026-08-14
Yes, if you manage Python packages and want to automate version bumping. The tool is lightweight, permissively licensed, and has no known vulnerabilities. Install friction is low and maintenance is current. The aging status (205 days since last release) is not a concern given the recent commit and stable feature set; version bumping is a mature, narrow problem. Suitable for both traditional setup.py and modern pyproject.toml workflows.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later; must be run in a directory containing setup.py or pyproject.toml with a version field.
- Low friction to install; the package has aged since its last release 205 days ago but remains actively maintained with a recent commit.
- Four lightweight runtime dependencies (click, first, packaging, toml) pose no installation burden.
License · maintenance · safety
permissive license (permissive) — MIT license permits commercial and private use with minimal restrictions, making it suitable for most development workflows.
last release 2026-01-21 (205 days) · last repo commit 2026-01-21 · 16 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 124,189 downloads/mo, #11,883 on PyPI
Alternatives
Verify before relying
$ pip install bump
$ bump
1.0.1
Or with options:
$ bump --minor --reset
2.0.0- Whether the tool handles version strings in formats beyond PEP 440 or custom version schemes.
- Performance characteristics when processing large or complex package metadata files.
- Behavior when both setup.py and pyproject.toml have conflicting version values.
What it is and what it does
Bump is a command-line tool that automates version number increments in Python package metadata files. It reads version strings from setup.py and pyproject.toml, applies semantic versioning rules (major, minor, patch), and writes the updated version back to both files in sync. The tool supports configuration files (.bump or setup.cfg) to avoid repeating command-line options, and integrates with modern packaging tools like uv, poetry, and flit while maintaining backward compatibility with traditional setup.py-only projects.
You run it as a simple command in your project root—bump returns the new version number so you can capture it for release workflows, git tags, or environment variables. It handles pre-release identifiers and local version segments, and can reset subversions (e.g., bumping major from 1.2.3 to 2.0.0 instead of 2.2.3). The package depends on click for CLI handling, packaging for version parsing, toml for configuration, and first for utility functions.
Use it for
- Automate version bumps in CI/CD pipelines before building and publishing releases.
- Keep setup.py and pyproject.toml synchronized during development without manual editing.
- Generate version numbers for git tags and release notes in shell scripts or Makefiles.
- Enforce consistent semantic versioning across a project without manual version string management.
- Configure per-project bump rules in .bump or setup.cfg to standardize team workflows.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you manage Python packages and want to automate version bumping.
The tool is lightweight, permissively licensed, and has no known vulnerabilities. Install friction is low and maintenance is current. The aging status (205 days since last release) is not a concern given the recent commit and stable feature set; version bumping is a mature, narrow problem. Suitable for both traditional setup.py and modern pyproject.toml workflows.
Install
bump on PyPI
Before you install
Low friction to install; the package has aged since its last release 205 days ago but remains actively maintained with a recent commit. Four lightweight runtime dependencies (click, first, packaging, toml) pose no installation burden.
Requires Python 3.10 or later; must be run in a directory containing setup.py or pyproject.toml with a version field.
License in practice
MIT license permits commercial and private use with minimal restrictions, making it suitable for most development workflows.
Quickstart
$ pip install bump
$ bump
1.0.1
Or with options:
$ bump --minor --reset
2.0.0Verify before relying
- Whether the tool handles version strings in formats beyond PEP 440 or custom version schemes.
- Performance characteristics when processing large or complex package metadata files.
- Behavior when both setup.py and pyproject.toml have conflicting version values.
Package facts
| License | permissive license permissive |
| Python support | Supports the current Python release >=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 4 packagesclickfirstpackagingtoml |
| Maintenance | Aging 205 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 124,189 / month, #11,883 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | License :: OSI Approved :: MIT LicenseProgramming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12 |
Evidence: bump-1.4.0-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “setup.py version updater”
- bumpAutomatically increments version numbers in setup.py and…
- bumpversionA command-line tool that automates version bumping by updating…
- bump2versionA command-line tool that automates version bumping across your source…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also bump-my-version · pip-upgrader · tbump · bumpversion · bump2version · semver · bumpver · version-parser · release-tag · node-semver