toko-tooling 0.44.8

Shared development tools, CI helpers and engineering rules for Toko Studios
Documentation

toko-tooling

The source distribution of Toko Studios development tooling: scripts, Make interfaces, CI actions, catalogs, rules, licenses and guides. Its empty Rust library is dependency-free and no_std, with no build script.

The package's authoritative licence is provided in LICENSE.md. See the licensing guide.

Select an exact reviewed release once in repository-root Cargo.toml. The example below uses published 0.43.2; it is not an automatic latest-version selector:

[workspace.dependencies]
toko-tooling = "=0.43.2"

Every real workspace package inherits it as a dev-dependency:

[dev-dependencies]
toko-tooling.workspace = true

[package.metadata.cargo-machete]
ignored = ["toko-tooling"]

Merge existing exemptions. A standalone package declares the exact version in its own dev-dependencies instead. No helper packages or Rust imports are needed. cargo update -v reports newer available releases; the exact pin keeps adoption intentional. For an installed consumer, change the pin in each maintained workspace, run make deps-update DEPENDENCY_PACKAGE=toko-tooling, then make toko-tooling-preview and make toko-tooling-update. This updates the root and independent qualification locks. Cargo.lock supplies the version and checksum; installation downloads and authenticates the actual crates.io source payload.

For first installation, these Make commands are not available yet. Prepare the prerequisites and use the installer from a reviewed producer checkout or authenticated crate extraction, following the initial adoption guide. Install selected executables under vendor/toko-tooling/ and include vendor/toko-tooling/make/consumer.mk. Reference guides stay upstream; the baseline and canonical licence/contribution files retain their root locations.

make toko-tooling-install installs the existing Cargo.lock selection. Offline make toko-tooling-check validates every member's declaration, the root pin, Cargo.lock and installed files. Common CI/release entrypoints require it; Cargo builds never install tools. The producer qualifies its source archive instead of depending on itself.

Follow the migration guide to remove the 0.34–0.35 metadata tables and toko-tooling.lock, plus any old selection-only packages. Real tools and qualification packages remain. Releases before 0.33 contain only a marker; 0.36 introduces this Cargo-visible per-package selection contract.