Skip to main content

updv

tiny version string updater written in python.

updv updates a version string across a project from a single version value, using a configurable TOML-based configuration file. this keeps version values in source files, package metadata, documentation, and other project files synchronized.

features

  • toml-based configuration (.updv.toml)
  • simple getopt-based cli frontend
  • update multiple files from a single version value
  • configurable file creation and failure behavior
  • templated paths, patterns, and replacements
  • minimal runtime dependencies

dependencies

updv requires at least

  • a python 3.11 or newer interpreter

development dependencies include

  • pytest: to execute the unit tests

installation

clone the repository and install updv in editable mode.

python -m pip install -e .

configuration

create a project configuration from the included example:

cp updv.toml.example .updv.toml

edit .updv.toml to define which files and version values updv should update.

example .updv.toml:

[project]
name = "hello"
version = "0.0.0"
previous_version = "0.0.0"

[project.files.initpy]
path = "src/{name}/__init__.py"
on-missing-file = "fail"
on-no-match = "fail"
enabled = true

pattern = "__version__ = \"{old}\""
replacement = "__version__ = \"{new}\""

[project.files.changelog]
path = "CHANGELOG.md"
on-missing-file = "fail"
on-no-match = "skip"
enabled = true

pattern = "## \\[Unreleased\\]"
replacement = "## [{new}] - {date}"

[project.files.version]
path = "VERSION"
on-missing-file = "create"
on-no-match = "write"
enabled = true

pattern = "{old}"
replacement = "{new}"

paths, patterns, and replacements support project and version variables such as {old}, {new}, {version}, {name}, and {date}.

policies

on-missing-file

  • create: create an empty file
  • skip: skip the file
  • fail: fail with an error

on-no-match

  • append: append the replacement to the file
  • prepend: prepend the replacement to the file
  • write: overwrite the file with the replacement
  • skip: skip the file
  • fail: fail with an error

usage

updv -n 0.2.0 # updates version values to 0.2.0
updv -h # view all available cmd options

testing

running the test suite can be done with pytest

pip install -e ".[dev]" # install dev dependencies
pytest -vs . # run the unit tests

project status

updv is in active development. while functional, it is not yet production-ready for real-world usage.

license

BSD-3-Clause, see LICENSE

Release files for updv 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for updv 0.3.0
File Size Uploaded
updv-0.3.0.tar.gz 11.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for updv 0.3.0
File Interpreter ABI Platform
updv-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 19.9 kB

Release files / updv-0.3.0.tar.gz

Download URL updv-0.3.0.tar.gz
Size 11.1 kB
Tags Source
SHA-256 checksum
How to use checksums
f7f519835e3c64e065b2520e34219aa582a7c9992bfd0ac6378e92349d17c917
BLAKE2b-256 checksum
How to use checksums
e19fd03bb06f4106a50447fc3393e045fd1ca3e3ecd26cc99c60b048e94a7a9b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.

Transparency log

Release files / updv-0.3.0-py3-none-any.whl

Download URL updv-0.3.0-py3-none-any.whl
Size 8.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
90bf756c7533f6b2bee89f6dfcc1d8fbccc124516b3fbe6970f5495a45ffdf51
BLAKE2b-256 checksum
How to use checksums
653c4e725a8a9d95f676bd542aaa0c304946956bec923cb86039c513c873828f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.

Transparency log

Release history Release notifications | RSS feed

0.4.0

2 release files

This release

0.3.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page