`git cliff --unreleased --bumped-version` reads the conventional commits since the last tag and prints the version they imply; `cargo release` writes it into Cargo.toml and Cargo.lock, commits it, and creates an annotated tag. CONTRIBUTING.md carries the single command that joins the two. cliff.toml sets breaking_always_bump_major = false, which is the point of the file. git-cliff defaults it to true and its docs are explicit that this covers the 0-to-1 transition, so with five `!` commits in range the first bump would be 1.0.0. Checked rather than inferred: the same command prints v1.0.0 without that line and v0.2.0 with it. 1.0.0 is a promise this project has not made. release.toml turns off everything that leaves the machine. publish = false was confirmed by flipping it - true reaches the crates.io index and dies on a missing token, false never opens a socket. None of this has run against the real repo, which has no tag yet for it to count from.