YantrikDB

v0.6.1 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 1mo AI Agents & Assistants

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

agent-memory ai-agents anthropic claude-code cognitive-memory database

+12 more

embeddings hnsw knowledge-graph llm llm-memory mcp memory persistent-memory python rust semantic-memory vector-db

Affected surfaces

auth breaking_upgrade

Summary

AI summary

Fixed silent overwrite of multi-source claims, allowing contradictory polarity assertions.

Full changelog

Critical Bug Fix

Multi-source claims now coexist as intended

The V17 UNIQUE(src, dst, rel_type) constraint on the claims table caused ingest_claim() to silently overwrite any previous source's claim whenever another source asserted the same (src, rel_type, dst) — destroying the exact polarity contradiction cases that RFC 006 is designed to detect.

Impact: Before this fix, a witness denying a fact (polarity=-1) and a log confirming it (polarity=+1) could not coexist. The second insert would silently overwrite the first. Multi-source investigation was impossible.

Fix (schema V18): Widens the constraint to UNIQUE(src, dst, rel_type, extractor, polarity, namespace). Now each source can assert its own claim, positive and negative claims about the same fact coexist, and namespaces are properly isolated.

New

`get_conflicts` accepts a namespace filter

YantrikDB::get_conflicts() now takes an optional namespace parameter. Scoped investigations can surface only the contradictions relevant to a specific case without cross-tenant noise.

Breaking changes

YantrikDB::get_conflicts() signature gains a namespace parameter before limit. Pass None to preserve prior behavior.

Full Changelog

https://github.com/yantrikos/yantrikdb/compare/v0.6.0...v0.6.1

Breaking Changes

`YantrikDB::get_conflicts()` signature gains a `namespace` parameter before `limit`. Pass `None` to preserve prior behavior.

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track YantrikDB

Get notified when new releases ship.

About YantrikDB

All releases →

Related context

Related tools

Earlier breaking changes

v0.7.20 `correct()` now mutates in place, preserving rid and adding revision history (BREAKING CHANGE).
v0.7.9 Pure-additive; existing engines keep English models on v0.1.0.