Version and specifier math built on packaging. Prereleases (a/b/rc/.dev), epochs, local versions, and PEP 503 name normalization are handled the way pip and uv actually resolve them.

A fixpoint release-plan engine bumps dependents across your workspace and rewrites their PEP 508 constraints. A dependent is released when the new version leaves its declared range, and not before.

Workspace members are discovered from your uv layout, and uv.lock is refreshed in the same commit that bumps a version, so a --frozen install in CI still resolves.

Most Python projects ship one package, so that is molt's default path. molt init, add, version, and publish work end to end with no workspace configuration.

add, version, publish, build, and git-tag each produce a machine-readable plan. Pass --dry-run to print exactly what would happen and write nothing to disk.

molt version --pre rc cuts release candidates for one run. There is no mode to enter or exit and no state file to commit, and the spellings map onto PEP 440.

PyPI keeps every version forever. molt yank checks the version, reports whether it is already yanked, and prints the PEP 592 steps. PyPI publishes no yank API, so the last click is yours.

2,104 tests cover the release-plan engine, the CLI, the changelog, and the publish path, with property-based cases over PEP 440 bump math.