Release history
pomazanbohdan/memory-mcp-1file releases
A self-contained Memory server with single-binary architecture (embedded DB & models, no dependencies). Provides persistent semantic and graph-based memory for AI agents.
All releases
48 shown
async-trait removal + concurrency fixes
- Existing databases from v0.2.x are NOT compatible due to schema changes; re-index data or start with a fresh database.
- All tables are now SCHEMAFULL for stricter validation.
- Strict enforcement of RecordId types; Thing struct updated to SDK v3 requirements.
- Deprecated IS NOT NULL syntax replaced with IS NOT NONE.
- Full compatibility with surrealdb crate v3.0.0 and surrealdb-types v3.0.0.
- `memories` table tracks superseded_by and valid_until fields.
- `symbol_relation` table includes source locations (file_path, line_number) and timestamps.
Full changelog
This release marks a major upgrade to SurrealDB v3.0.0, bringing strict schema validation and improved type safety.
🚨 Breaking Changes
- Database Schema: All tables are now
SCHEMAFULLfor stricter validation. - Type Handling: Strict enforcement of
RecordIdtypes.Thingstruct usage updated to match SDK v3 requirements. - Query Syntax: Deprecated
IS NOT NULLsyntax replaced withIS NOT NONE.
✨ Features & Improvements
- SurrealDB v3 Support: Full compatibility with
surrealdbcrate v3.0.0 andsurrealdb-typesv3.0.0. - Enhanced Schema:
memoriestable now trackssuperseded_byandvalid_until.symbol_relationtable now includes source locations (file_path,line_number) and timestamps.
- Robustness:
reset_dboperation is now atomic per-table, preventing failures when tables are missing.- Fixed N+1 query issues in relation fetching.
- Implemented manual
Value::Objectdeserialization to bypass SDK limitations withRecordId.
🛠️ Fixes
- Fixed serialisation issues where
RecordIdfields inRelationandSymbolRelationwere not parsing correctly. - Addressed 70+ compilation errors related to the SDK upgrade.
- Verified 73/73 unit tests passing.
Upgrade Guide:
Existing databases from v0.2.x are NOT compatible due to schema changes. Please re-index your data or start with a fresh database.
Idle timeout disabled, reconnect loop removed