multicz
Multi-component versioning for monorepos.
Bump a Python app, its Docker image, and the Helm chart that deploys it from a single conventional-commit history - each with its own version line and its own git tag.
Install
uv tool install multicz # or: pipx install multicz / pip install multicz
Quickstart
# 1. scaffold a multicz.toml in the repo root
multicz init
# 2. see what would bump from the current commit window
multicz changed
multicz explain api
# 3. apply the bump (writes version files + changelog, commits, tags)
multicz bump --commit --tag
# 4. ship it
git push --follow-tags
For multi-component setups (api + chart, app + image + helm, ...), declare
each component's paths in multicz.toml and let mirrors and triggers cascade
related versions. See the docs for the
full configuration reference.
What it does
- Per-component versions - each component has its own version line and
its own git tag (
api-v1.2.0,chart-v0.5.0). - Conventional-commit driven -
feat:→ minor,fix:→ patch,BREAKING CHANGE:→ major. Scopes route the bump to the right component. - Mirrors and triggers - bump api
1.2.0→1.3.0and the Helm chart'sappVersionfollows; the chart's own version cascades a patch. - No network, no auto-updates. Pure
git+ filesystem. Same input yields the same plan byte-for-byte.
Documentation
Published at https://goabonga.github.io/multicz/:
- Get started - install, minimal config, first bump
- Concepts - components, mirrors, triggers, cascades, bump policies
- Configuration - full
multicz.tomlreference - CLI - every command and flag
- Recipes - FastAPI + Helm walkthrough, CI matrix gating, release candidates
- Why multicz? - vs. semantic-release, Commitizen, Changesets, bump-my-version
- Security - guarantees and CI hardening
License
1 maintainer
Metadata
1 maintainer
Release files for multicz 1.7.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| multicz-1.7.1.tar.gz | 95.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| multicz-1.7.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 239.1 kB
Release files / multicz-1.7.1.tar.gz
| Download URL | multicz-1.7.1.tar.gz |
|---|---|
| Size | 95.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f8c98b0d6120a86ab2a77f07682726bb45f62dbdb238f369ea9d59a133b1a018
|
|
BLAKE2b-256 checksum How to use checksums |
e2ac0a55972c94d34e5f50b59e217d519963d5b78a8083ee8d518fe085b0d002
|
| 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 Oct 6, 2026.
Transparency logRelease files / multicz-1.7.1-py3-none-any.whl
| Download URL | multicz-1.7.1-py3-none-any.whl |
|---|---|
| Size | 143.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
81c21f979ccf4563b39d7d5d6c29fd1bcfab432bfbbab480052d46de1a9f2436
|
|
BLAKE2b-256 checksum How to use checksums |
596d8fc15f745bb72df293393646e570e87e93c1104ae36a32acc1958ddd5936
|
| 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 Oct 6, 2026.
Transparency logSecurity for multicz 1.7.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for multicz-1.7.1.tar.gz
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 Oct 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
