oakum 0.12.1

A polyglot release tool that derives dependent version bumps from the dependency graph
Documentation
//! Release planning across package ecosystems.
//!
//! The planner is a pure function from intent (change files or conventional
//! commits) plus a discovered workspace to a release plan. Everything that
//! touches the filesystem, a registry, or GitHub lives outside it, so the
//! cascade math can be tested against recorded history without side effects.
//!
//! Modules are named for the crates they would become if this is ever split;
//! see `docs/contributing/structure.md` for what would trigger that.

// `plan` is written against `alloc` rather than `std` so that extraction under
// ADR-0024 is a file move: `alloc` supplies what a `no_std` prelude does not.
// Declared at the crate root, which is what puts `alloc::` in scope for `plan`.
extern crate alloc;

pub mod changeset;
pub mod commits;
pub mod config;
pub mod detect;
pub mod discover;
pub mod manifest;
pub mod plan;
pub mod prettier_json;
pub mod state;
pub mod tags;
pub mod template;

// Scoped to the test module rather than a file, as `clippy.toml` directs: this
// is a fixture guard that creates and removes its own temp tree, not an I/O
// boundary the library crossed.
#[cfg(test)]
#[expect(
    clippy::disallowed_methods,
    reason = "the unit-test fixture guard owns the temp tree it creates, chmods, and removes"
)]
mod test_fixture;