Crates Overview

Runi is a Cargo workspace. Most callers depend on runi-core — which is both the foundation crate and, via feature flags, a bundle that re-exports the rest of the workspace. The sub-crates can also be used directly if you prefer narrower dependencies. Crates share a single workspace version (see Versioning below) and each has its own entry on docs.rs.

Following the wvlet/uni pattern, runi-core plays the dual role of "foundation" and "one-line bundle" so users can write runi = { package = "runi-core", ... } in their Cargo.toml and reach every workspace crate through the clean runi:: namespace. See the runi-core page for the full alias pattern.

How they fit together

• runi-core carries the foundation types (Error, Result, Config, str_util) and bundles every other workspace sub-crate behind a feature flag of the same name. All bundled features are on by default. The canonical list of bundled features lives on the runi-core page.
• The bundled sub-crates are independent leaves — they don't depend on runi-core or on each other, so picking individual crates directly is always an option.
• runi-test is a dev-dependencies-only helper and is not part of the bundle. Depend on it directly in your [dev-dependencies].

Versioning

Runi uses unified workspace versioning — every crate shares the same version and they are released as a set. The version is defined once in the workspace Cargo.toml ([workspace.package]) and inherited by each member. Intra-workspace dependencies live in [workspace.dependencies].

All crates currently track 0.1.x. When the workspace bumps, every crate bumps together — pick a single version for all four runi-* entries in your Cargo.toml. Breaking changes will be called out in each crate's CHANGELOG.md (coming soon).

Independent per-crate versioning can be adopted later if release cadences diverge; for now the set moves as one.