# Install bump-my-version with Homebrew, Nix

Version bump your Python project. Version 1.5.0 via Homebrew; verified 2026-07-28. Also installable with nix: nix profile install nixpkgs#bump-my-version.

## Install

```sh
sudo av install brew:bump-my-version
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install bump-my-version
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#bump-my-version
```

  Evidence: nixpkgs package indexes: pkgs/by-name/bu/bump-my-version/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:bump-my-version
- **Package manager:** Homebrew
- **Version:** 1.5.0
- **Source summary:** Version bump your Python project
- **Homepage:** <https://callowayproject.github.io/bump-my-version/>
- **Repository:** <https://github.com/callowayproject/bump-my-version>
- **Last updated:** 2026-07-28T21:44:22Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- bump-my-version (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 1.5.0
## Project history and usage

Bump My Version is a Python release-automation CLI for changing version strings across project files, then optionally committing and tagging the result.

### Project history

The project appeared publicly in April 2023 as a continuation of the long-running bumpversion-style workflow for Python projects. Its repository description calls it a small command-line tool for updating all version strings in source code by the correct increment and optionally committing and tagging the change.

The documentation keeps compatibility with legacy `.bumpversion.cfg` and `setup.cfg` configuration while recommending TOML configuration such as `.bumpversion.toml` and `pyproject.toml`. That places it in the Python packaging transition from setup.cfg-era projects toward pyproject.toml-era tooling.

### Adoption history

Adoption is concentrated among Python projects that want a maintained bumpversion-compatible tool without building custom release scripts. Homebrew and Nix packaging make it available outside Python-only installation paths, but its main audience remains developers standardizing release bumps in source-controlled projects.

### How it is used

A typical workflow defines the current version, parsing rules, files to edit, and optional commit/tag settings in configuration. Developers then run the CLI to bump major, minor, patch, calendar, or custom version components and let the tool update matching files consistently.

### Why package nerds care

Bump My Version matters because version bumpers sit at the boundary between package metadata and Git history. They encode how maintainers synchronize package versions, changelogs, tags, and source files, which is one of the least glamorous but most failure-prone parts of publishing packages.

### Timeline

- 2023-04: Public GitHub repository created.
- 2023-06: Early 0.x releases established the CLI and replacement behavior.
- 2023-08: 0.9.x releases expanded documentation and regular-expression support.
- 2026-06: 1.4.x releases show ongoing maintenance.

### Related projects

- Related projects include the original bumpversion family, bump2version, Python build backends that read `pyproject.toml`, and release automation tools such as semantic-release, towncrier, and conventional changelog generators.

### Sources

- <https://callowayproject.github.io/bump-my-version>
- <https://callowayproject.github.io/bump-my-version/reference/configuration/>
- <https://github.com/callowayproject/bump-my-version>
- <https://github.com/callowayproject/bump-my-version/releases>


## Security Notes

No matching local secret-handling manifest was found for bump-my-version. Nucleus package metadata is still published here so future coverage has a stable package URL.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: --config-file <FILE>, $BUMPVERSION_CONFIG_FILE, .bumpversion.cfg, .bumpversion.toml, setup.cfg, pyproject.toml
## Other Package-Manager Records

- Nix - bump-my-version: normalized package name match | nixpkgs package indexes: pkgs/by-name/bu/bump-my-version/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/bump-my-version.yml](https://github.com/mxcl/pkgdb/blob/main/combined/bump-my-version.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph