mirror of
https://github.com/hanzoai/ml.git
synced 2026-11-20 23:08:29 +00:00
The rule: each crate carries its own version and moves by a PATCH bump from the version it last released to crates.io. Crates change at different rates, so their numbers differ -- hanzo-ml has shipped 95 times and hanzo-3d once. That is information, not drift, and renumbering a crate to match another would both discard it and burn a breaking-position bump (0.2 -> 0.11 is nine of them) to say nothing new. The tag names the release event; the manifests name the artifacts. crates.io is the registry. No [registries] in .cargo/config.toml, no publish allow-list in any manifest, and hanzoai/engine publishes the same way. Publishing walked a hand-written crate list, and hanzo-kernel was missing from it: only hanzo-kernels (plural, the CUDA kernels) was listed, never hanzo-kernel (singular, the kernel DSL). A crate absent from that list never reaches the registry, so it drifted to 0.2.20 on crates.io against 0.2.39 in tree. Adding the one name back would leave the mechanism that lost it, and seven more crates were already missing the same way -- hanzo-datasets, hanzo-onnx, hanzo-transformers, hanzo-training, hanzo-3d, hanzo-bindgen-cuda, hanzo-research. So the list is now derived. scripts/publish-order reads every manifest, drops the ones that say `publish = false`, and topologically sorts what is left over the dependency edges already written there. A crate publishes because it exists. cargo metadata cannot answer this alone: the kernel crates carry `links=` build scripts and so sit in the workspace `exclude` list, invisible as members while still being crates we publish. `publish = false` becomes the one way to opt out, and says why in each manifest. Fifteen crates take it -- the examples, the nine browser demos, the book, the wasm test harness, hanzo-train (a binary), hanzo-ml-pyo3 (it ships to PyPI via maturin) -- and tensor-tools, whose crates.io name belongs to the upstream candle author, so that one can never be published from here at all. The release set is 18. Also: `cargo add hanzo-ml-core` was the documented way in, and no such crate exists in the tree or on crates.io. It is `hanzo-ml`.
22 lines
540 B
TOML
22 lines
540 B
TOML
[package]
|
|
name = "tensor-tools"
|
|
# Not published: the crate name `tensor-tools` on crates.io belongs to the upstream candle author, not Hanzo.
|
|
publish = false
|
|
version.workspace = true
|
|
edition.workspace = true
|
|
description.workspace = true
|
|
repository.workspace = true
|
|
keywords.workspace = true
|
|
categories.workspace = true
|
|
license.workspace = true
|
|
|
|
[dependencies]
|
|
anyhow = { workspace = true }
|
|
hanzo-ml = { workspace = true }
|
|
clap = { workspace = true }
|
|
rayon = { workspace = true }
|
|
safetensors = { workspace = true }
|
|
|
|
[lints]
|
|
workspace = true
|