chore(release): v0.7.1 — lattice 0.7.0 dependency adoption - #1648
Closed
ohdearquant wants to merge 3 commits into
Closed
chore(release): v0.7.1 — lattice 0.7.0 dependency adoption#1648ohdearquant wants to merge 3 commits into
ohdearquant wants to merge 3 commits into
Conversation
Owner
Author
|
Superseded: the lattice dependency adoption and constant rename landed on main via #1661 against lattice 0.7.1 (this branch pinned 0.7.0), and the remaining workspace version bump belongs in a fresh release cut at release time. Closing rather than rebasing a stale release branch. |
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
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.
Release 0.7.1: adopt the published lattice 0.7.0 crates.
Changes
lattice-embedandlattice-fannrequirements bumped to
0.7.0(published on crates.io; verified on theindex per crate against the 0.6.1 pre-state). Lockfiles regenerated,
including the excluded
khive-mergeworkspace.the workspace floor.
MAX_TEXT_CHARS→MAX_TEXT_BYTESacross 10 files, following thelattice-embed 0.7.0 deprecation (same 32768 value; the constant counts
UTF-8 bytes, which is what the byte-based production guard always
enforced — behaviorally identical admission set).
crates/targetsymlink that had been committed (atarget/gitignore pattern matches directories only, not symlinks).Compatibility gate (run before the lattice release was published)
Against the lattice 0.7.0 release candidate, with the patch resolution
hard-asserted via
cargo metadata(a[patch.crates-io]entry whoseversion does not satisfy the requirement is silently ignored — the gate
aborts rather than green-lighting a registry build):
khive: the sole production ingress guard was already byte-based, and
chars ≤ bytes in UTF-8 means an identical admission set.
Verification on this branch
make cigreen end to end (no-stub guards, lockfile freshness,forward-deployed crate checks, fmt, lints, full test suite, release
build, contract tests: 127 passed).
comm.sendmedian 776µs / p95 993µs (bounds 8.5ms / 11ms),comm.replymedian 891µs / p95 1.15ms (bounds 9.5ms / 12.5ms).