chore: release 0.17.0 - #1193
Closed
ajianaz wants to merge 1 commit into
Closed
Conversation
Version bump 0.16.0 -> 0.17.0 across the workspace; internal dep requirements (uteke-core/uteke-mcp) bumped to 0.17.0. Minor release theme: inspectable, trustworthy memory. Added: - explain recall on CLI/HTTP/MCP (#1160) - contradiction resolution ledger + undo, edge-driven (#1172 F2) - contradiction benchmark segment + uteke supersede CLI (#1172 F3) - /list pagination metadata envelope (#1188) - provenance data model, schema v18 (#1172 F1) Fixed: - graph excludes stale memory nodes; readable node labels (#1189 #1187) - dual-engine vector layer documented: UTEKE_VECTOR_BACKEND env or [vector] backend in uteke.toml switches usearch/vecq at runtime with automatic index rebuild (#1168, shipped in 0.16.0; now in configuration.md)
🔍 Cora AI Code Review✅ No issues found. Code looks good! Review powered by cora-code · BYOK · MIT |
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.
What
Release prep for 0.17.0 — version bump across the workspace (0.16.0 → 0.17.0), internal dep requirements updated, CHANGELOG dated, and the dual-engine vector docs completed (
[vector] backendsection in configuration.md).No code changes in this PR — all features below are already merged and individually CI-green on develop.
Why
Cut the 0.17.0 minor release per #1165 (vecq-core 0.3 already pinned on develop and validated against crates.io).
Contents of 0.17.0 (all merged to develop)
Added
--explain/explain: true/ MCPexplainon every recall surface; per-result ranking signals (vector sim + rank, FTS rank, RRF contributions, boost deltas)GET /contradictions,POST /contradictions/undo, CLIcontradictions list|undo, MCP toolscontradiction_segment.py+ published RESULTS.md section; fusion winner@1 0.850 → 1.000, stale@5 1.000 → 0.000 after supersedeuteke supersedeCLI (feat: contradiction benchmark segment + uteke supersede CLI (#1172 F3) #1192) — surface parity (was MCP/HTTP only)/listpagination metadata (server: /list pagination metadata (total / has_more / next_offset) - clients blind-paginate #1188, feat: /list pagination metadata envelope (#1188) #1191) — opt-ininclude_metaenvelopesource_hash, actor/evidence chain,GET /provenance, CLI + MCP toolsFixed
Dual-engine vector (validation this release)
UTEKE_VECTOR_BACKEND=usearch|vecqenv or[vector] backendin uteke.toml switches engines at runtime with automatic index rebuild from SQLite (#1168). Validated for 0.17.0: vecq-core 0.3.0 = main (crates.io), merge gate green (59 tests dbg+release, fmt, clippy -D warnings, real benchmark r@1 0.940 / r@10 0.974 / 4.78x = BENCHMARK.md baseline), utekevecqfeature builds + E2E store→index→recall green on both engines.Testing
cargo test --workspace— 667 passed, 0 failed (release-commit build)cora reviewpass (pre-commit + CI)