Changelog
Changelog
All notable changes to Memory Service are documented here.
This project follows Semantic Versioning.
Unreleased
Changes in the main branch that are not yet released.
Added
- Initial documentation site with versioned docs support
- Astro-based static site with Tailwind CSS v4
- MDX support for interactive documentation
Changed
- Documentation is now hosted on GitHub Pages
Pre-release Development
Memory Service is currently in active development and has not yet reached version 1.0.0. APIs and features may change.
Current Features
- Conversation Storage - Store and retrieve conversation history with PostgreSQL, SQLite, and MongoDB
- Entry Management - Append-only entries with full conversation context
- Conversation Forking - Fork conversations at any entry
- Semantic Search - Vector-based search via pgvector, sqlite-vec, and Qdrant
- Full-Text Search - Keyword-based search across indexed content
- Access Control - User-based permissions and sharing with ownership transfer
- Episodic Memories - Namespaced key-value store with OPA/Rego policies and vector indexing
- Encryption at Rest - AES-GCM encryption for stored entries and memory values
- Response Recording and Resumption - Streaming responses survive client reconnects
- File Attachments - Server-stored files with signed download URLs
- Caching - Local, Redis, and Infinispan cache support
- APIs - REST and gRPC interfaces
- Framework Integrations - Quarkus LangChain4j, Spring AI, Python LangChain/LangGraph, TypeScript Vercel AI
Version Format
Version numbers follow the pattern vX.Y.Z:
- X (major): Breaking API changes
- Y (minor): New features, backward compatible
- Z (patch): Bug fixes, backward compatible
How to Upgrade
When upgrading between versions:
- Check this changelog for breaking changes
- Update your dependencies
- Run your test suite
- Review any deprecated APIs
For detailed upgrade guides, see the relevant version’s documentation.