Skip to content

One binary · macOS, Linux, Windows

One version.
Every file.
One command.

vump writes your new version into package.json, Cargo.toml, pyproject.toml and their lock files at once — then commits, tags, and verifies the tag in CI.

~/widget
$ vump patch --through tag
✓ 0.2.0 -> 0.2.1
Cargo.toml
Cargo.lock
✓ committed chore: bump version to v0.2.1
✓ tagged v0.2.1
Knows these files
package.jsonpackage-lock.jsonCargo.tomlCargo.lockpyproject.tomluv.lock*.csprojDirectory.Build.propsVERSION

What it does

Releases that never miss a file.

A version number usually lives in more than one place. vump moves all of them together, so the tag you push describes the code you built.

Every file at once

One command writes the new version into every file that records it, lock files included. Nothing is left half-bumped, and nothing is left to finish by hand.

vump minor

Guided, or completely silent

Run vump on its own and it asks what to bump, then shows you the plan before it touches anything. Name the bump and it asks nothing at all — which is what makes it safe in a script.

vump patch

Commit, tag, push

Carry the bump as far as you want in the same run. Or write the files only, and handle git yourself.

vump patch --through push

Works with

Your files, changed one line at a time.

Files are recognized by name — no configuration beyond listing them. Only the version moves: formatting, key order and comments stay exactly where they were.

package.json
{
"name": "@acme/widget",
"version": "1.4.0",
"dependencies": {
"react": "^19.0.0"
}
}

Monorepos, project by project

Name each project in vump.toml and they version independently, from anywhere in the repository.

vump.toml
[[project]]
name = "api"
files = ["services/api/Cargo.toml", "Cargo.lock"]
 
[[project]]
name = "web"
files = ["apps/web/package.json"]
~/monorepo
$ vump status
✓ api 1.4.2
✓ web 0.9.0
$ vump patch --project api
✓ 1.4.2 -> 1.4.3

In your pipeline

Three lines that stop a bad tag.

Push a tag and the action checks it against the version in your source. Put it first in the job, and a tag that does not match costs seconds instead of a whole release.

.github/workflows/release.yml
on:
push:
tags: ['v*']
 
jobs:
release:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: codehacks-io/vump/.github/actions/check@main
with:
version: ${{ github.ref_name }}
 
- run: cargo build --release

When the tag and the source disagree

ci · verify
$ vump check v1.4.0
✗ version mismatch: expected 1.4.0
✗ Cargo.toml 1.3.2
✓ package.json 1.4.0

The job stops right there. Nothing is compiled, signed or published under a version that was never in your source.

Quick start

Three steps, once.

01  Install it

Grab a binary for your platform, or build it from source.

Download v0.8.1
git clone https://github.com/codehacks-io/vump
cd vump && cargo install --path .

02  Point it at your files

vump init finds the files that record your version and writes them into a config you can edit.

~/your-repo
$ vump init
✓ wrote vump.toml tracking:
Cargo.toml
Cargo.lock

03  Bump

Run vump and pick a bump, or name one and skip the questions.

$ vump — guided

$ vump patch — no questions

$ vump patch --through push

Flags, configuration and everything else live in the manual.

Read the docs