Introduction

lading is a command-line tool for managing release workflows in Rust workspaces. It can:

• Bump versions across the workspace (Cargo.toml files) and keep internal dependency requirements in sync.
• Update version references inside TOML code fences in Markdown documentation.
• Plan and execute publication (cargo package + cargo publish) in dependency order, with pre-flight cargo check/cargo test validation.

Breaking change in 0.1.0 — --live interleaving

Prior to 0.1.0, lading publish --live ran a two-phase pipeline: all crates were packaged before any were published. From 0.1.0 onwards the live pipeline is interleaved — each crate is packaged and published in turn before the next crate is processed. Dry-run mode retains the original two-phase order. Workspaces that relied on the old sequencing must adopt the new per-crate ordering; no configuration knob restores the prior behaviour.

The 0.1.0 release also changes workspace README adoption:

Breaking change in 0.1.0 — workspace README adoption

Prior to 0.1.0, lading publish copied the workspace README.md into crates that set readme.workspace = true while preparing the staged workspace. From 0.1.0 onwards, lading bump performs that adoption and rewrites relative Markdown links before publishing. Commit the adopted crate README files produced by lading bump before running lading publish; publish staging no longer creates or repairs those files.