Files
ml/Cargo.toml
zeekay 6a0a3ab088 Every crate names its dependencies itself, and every published crate moves a patch
No crate inherits from the workspace any longer: each manifest holds its
own version, package fields, lints and dependency specs, siblings as a
path and the exact version they publish at. The root keeps members,
exclude, resolver and profiles. Every publishable crate takes a patch
bump so the registry carries manifests that stand alone.

Claude-Session: https://claude.ai/code/session_01JupC8d38f9Lkfz62hvjG2q
2026-10-06 14:44:26 -07:00

41 lines
1.1 KiB
TOML

[workspace]
# `exclude` holds the crates that cannot BE members: the kernel crates carry their own
# `links=` build scripts, and hanzo-ml-book is not a library. Everything else is a
# member, so `cargo test --workspace` and `cargo clippy --workspace` gate it. hanzo-onnx was
# excluded and therefore never built, tested or linted by CI — 64 op tests behind a lock nothing
# turned. It is a member; the `check`/`test`/`clippy` jobs install protoc for its build script.
members = [
"hanzo-3d",
"hanzo-datasets",
"hanzo-flash-attn-v3",
"hanzo-learn",
"hanzo-ml",
"hanzo-ml-examples",
"hanzo-ml-pyo3",
"hanzo-ml-wasm-examples/*",
"hanzo-ml-wasm-tests",
"hanzo-nn",
"hanzo-onnx",
"hanzo-research",
"hanzo-train",
"hanzo-training",
"hanzo-transformers",
"tensor-tools",
]
exclude = [
"hanzo-ml-book",
"hanzo-flash-attn",
"hanzo-flash-attn-build",
"hanzo-kernel",
"hanzo-kernel-macros",
"hanzo-kernels",
"hanzo-metal-kernels",
"hanzo-rocm-kernels",
]
resolver = "2"
[profile.release-with-debug]
inherits = "release"
debug = true