build(deps): bump lattice-embed and lattice-fann to 0.7.1 - #1661
Merged
Conversation
lattice-embed 0.7.x renames MAX_TEXT_CHARS to MAX_TEXT_BYTES: the limit always counted UTF-8 bytes, and the old name is now a deprecated alias that fails the clippy -D warnings gate. Rename all call sites accordingly (same value, 32768). Verified against the published crates: workspace check clean with zero warnings, and a byte-semantics probe over CJK input (char count under the cap, byte count over it) confirms rejection reports byte lengths against the published cap on both sides of the dependency boundary.
ohdearquant
marked this pull request as ready for review
August 2, 2026 21:57
….7.1 khive-merge maintains its own workspace and lockfile; the CI per-crate --locked compile check requires it to agree with the bumped manifest.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the two lattice dependencies from 0.6.0 to 0.7.1.
Changes
crates/Cargo.toml:lattice-embedandlattice-fannto"0.7.1"(MSRV unchanged at 1.93).MAX_TEXT_CHARS->MAX_TEXT_BYTESacross all 10 consuming files (44 occurrences). lattice-embed 0.7.x renames the constant because the limit always counted UTF-8 bytes; the old name survives only as a deprecated alias, which fails theclippy -D warningsgate. Same value (32768), same comparison — no behavior change.Verification
cargo check --workspace: clean, zero warnings after the rename.cargo clippy --workspace --all-targets -- -D warnings: clean.cargo fmt --all -- --check: clean.dot_product,euclidean_distance,squared_euclidean_distance, the resolved dot-product kernels, anddot_product_i8_raw. The files defining the f32 functions are byte-identical between v0.6.1-consumed code paths at v0.7.0 and v0.7.1; the quantized change is x86_64-only cfg-gating (compiles out on aarch64).Note for x86_64 deployments
0.7.x removes the compile-feature gate on the AVX-512 VNNI int8 dot kernel: hosts advertising VNNI now select it at runtime where earlier default builds fell back to AVX2. Accumulation order can differ for int8 dot products at high dimension. Only relevant where the quantized HNSW index runs on such hosts.