Hanzo Dev
cdccbacd40
The rust-sdk workspace (hanzoai/rust-sdk) just published these crate names at 1.1.21 with different implementations. To preserve clean namespaces: - crates.io name: hanzonet-pqc / hanzonet-did / hanzonet-config / hanzonet-mcp - Rust lib name: hanzo_pqc / hanzo_did / hanzo_config / hanzo_mcp (unchanged) This is achieved via `[lib] name = "hanzo_<x>"` on the renamed packages and `package = "hanzonet-<x>"` in workspace.dependencies — consumers keep using `hanzo-<x>.workspace = true` and `use hanzo_<x>::...` with zero code churn. Also: bumped patch versions on all members per crates.io state, pinned every path-dep in workspace.dependencies with a `version = ` so the workspace can publish to crates.io. workspace.package.version → 1.1.21. Effect: 32 net crates become publishable in topo order; hanzo-vm, hanzo-consensus, hanzo-l2 remain `publish = false` because they path-depend on cross-repo lux crates (luxprecompile-sys, lux-consensus) that aren't on crates.io.
22 lines
583 B
TOML
22 lines
583 B
TOML
[package]
|
|
name = "hanzo-models"
|
|
version = "1.1.13"
|
|
edition = "2021"
|
|
authors = ["Hanzo AI Inc"]
|
|
license = "MIT"
|
|
repository = "https://github.com/hanzonet/network"
|
|
homepage = "https://hanzo.ai"
|
|
description = "Model discovery for Hanzo AI platform"
|
|
|
|
[dependencies]
|
|
async-trait = "0.1"
|
|
reqwest = { version = "0.11", features = ["json"] }
|
|
serde = { version = "1.0", features = ["derive"] }
|
|
serde_json = "1.0"
|
|
tokio = { version = "1.35", features = ["full"] }
|
|
chrono = { version = "0.4", features = ["serde"] }
|
|
regex = "1.10"
|
|
percent-encoding = "2.3"
|
|
|
|
[dev-dependencies]
|
|
tokio-test = "0.4" |