---
id: bump
version: "1.4.0"
license: unclear
license_treatment: permissive
maintenance: aging
---

# bump — Bumps package version numbers

License: permissive · Maintenance: aging · Downloads: 124.2K/mo

## 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 above — verify before relying.

Automatically increments version numbers in setup.py and pyproject.toml files, supporting semantic versioning with options to bump major, minor, or patch versions.

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

pip install bump
uv add bump
poetry add bump

## Installing bump

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.

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.0

Requires Python 3.10 or later; must be run in a directory containing setup.py or pyproject.toml with a version field.

Verify 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: not declared (permissive)
- Python support: supports_current
- Install friction: low
- Maintenance: aging
- Downloads: 124.2K/month (top 15,000 on PyPI)
- Known vulnerabilities: none known

## Tags

version bumping tool, semantic versioning automation, setup.py version updater, pyproject.toml version sync, package version incrementer, release version management, automated version numbering, version-management, release-automation, packaging

[View on SkillFed](https://skillfed.io/packages/bump) · [View on PyPI](https://pypi.org/project/bump/)