✨ MemEX v0.10.1 — Hotfix Release
0.10 introduced hierarchical intents/tasks, direct memory ↔ intent/task links, and structural transplant.
0.10.1 fixes several correctness issues in transplant, contradiction filtering, updates, and time semantics.
Fixed
1. importSlice now correctly remaps intent_id / task_id on memory items
In 0.10.0, transplanted memory items could retain stale intent_id / task_id references when imported slices triggered re-ID of intents or tasks.
This happened because:
- Memories were imported before intents/tasks
- ID maps were not available yet
- Linked memories could end up pointing at non-existent entities
0.10.1 fixes cross-graph remapping during transplant so imported memories preserve valid intent/task links.
2. skipExistingIds: false no longer crashes on duplicates
In 0.10.0, disabling skipExistingIds could cause import to fall through into create on already-existing entities, raising duplicate errors.
0.10.1 fixes duplicate-handling behavior so this mode is usable.
3. filterContradictions no longer depends on insertion order in contradiction chains
Contradiction chains like:
A ↔ B ↔ C
Could produce different survivors depending on map insertion order.
0.10.1 makes contradiction filtering stable and deterministic for chained contradictions.
4. memory.update can now intentionally remove keys from content / meta
Previously, undefined values in merged updates were stripped too early, which made key removal impossible through the normal update path.
0.10.1 fixes update semantics so key deletion is no longer silently dropped.
5. Safer timestamp handling for user-supplied IDs
MemEX supports caller-supplied IDs, but non-UUIDv7 IDs could produce nonsense recency / decay behavior.
0.10.1 hardens time-based behavior around invalid or non-UUIDv7 IDs.
Upgrade
npm install @ai2070/memex@0.10.1