Files
zeekayandHanzo Dev fc2375c584 brand: the repo is hanzoai/index, so the product is Hanzo Index
The rename had left the repo half-named: README, CONTRIBUTING, SECURITY,
Cargo.toml, the issue templates and docs all still said "Hanzo Search" and
linked github.com/hanzoai/search.

Two things were worse than stale. The README credited the upstream engine to
"Index SAS" and said this repo is based on itself — a false attribution, fixed
back to Meili SAS and meilisearch/meilisearch. And the docs shipped a
TypeScript example importing `@hanzo/search`, a package that does not exist;
it is now the `fetch` calls that actually work.

`hanzoai/search-go` (a real repo) and `hanzoai/search-fts5` (named in the
Dockerfile as where a build lesson came from) are deliberately untouched.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-27 15:27:30 -07:00

66 lines
1.6 KiB
TOML

[workspace]
resolver = "2"
members = [
"crates/search",
"crates/searchtool",
"crates/search-types",
"crates/search-auth",
"crates/search-snap",
"crates/index-scheduler",
"crates/dump",
"crates/file-store",
"crates/permissive-json-pointer",
"crates/milli",
"crates/filter-parser",
"crates/flatten-serde-json",
"crates/json-depth-checker",
"crates/fuzzers",
"crates/tracing-trace",
"crates/xtask",
"crates/build-info",
"crates/openapi-generator",
"crates/http-client",
"crates/routes-macros",
"crates/routes",
"external-crates/async-openai",
"external-crates/async-openai-macros",
]
[workspace.package]
version = "1.45.2"
authors = [
"Hanzo AI <[email protected]>",
]
description = "Hanzo Index -- lightning-fast search engine for AI workloads"
homepage = "https://hanzo.ai"
repository = "https://github.com/hanzoai/index"
readme = "README.md"
edition = "2021"
license = "MIT"
[workspace.dependencies]
mimalloc = { version = "0.1.48", default-features = false, features = ["v3", "override"] }
[profile.release]
codegen-units = 1
[profile.release-with-debug]
inherits = "release"
debug = true
# We now compile heed without the NDEBUG define for better performance.
# However, we still enable debug assertions for a better detection of
# disk corruption on the cloud or in OSS.
[profile.release.package.heed]
debug-assertions = true
[profile.dev.package.flate2]
opt-level = 3
[profile.dev.package.grenad]
opt-level = 3
[profile.dev.package.roaring]
opt-level = 3
[profile.dev.package.gemm-f16]
opt-level = 3