Skip to content

Memind 0.2.0 Release Notes #136

Description

@me0106

Highlights

Memind 0.2.0 expands the project from a core memory engine into a broader memory platform for applications and coding agents.

Breaking Changes

  • JDBC artifacts and public APIs were restructured (Split JDBC plugin into dialect modules with Jdbi and Hikari-backed access #37). The former memind-plugin-jdbc implementation artifact is now a parent module. Applications must depend on memind-plugin-jdbc-sqlite, memind-plugin-jdbc-mysql, or memind-plugin-jdbc-postgresql; shared integrations can use memind-plugin-jdbc-core. JdbcStore, DriverManagerDataSource, and JdbcExecutor were removed. Plain Java applications must migrate to the relevant dialect plugin factory. Spring Boot applications can continue using memind-plugin-jdbc-starter.
  • The server API response contract changed (standardize server API response contract #65). Endpoints now return the standardized ApiResult success/error envelope, public error codes use snake_case, paging uses the new page result contract, and open memory APIs are split into synchronous and asynchronous controllers. Custom clients that parse bare response payloads or call the previous endpoint layout must be updated.
  • Retrieval cache APIs were removed (fix: remove retrieval cache #95). RetrievalCache, RetrievalConfig.enableCache(), RetrievalConfig.withoutCache(), and the cache-accepting DefaultMemoryRetriever constructors no longer exist.
  • Spring AI model configuration and wiring changed (refactor: route Memind AI through Spring beans #128). Memind no longer constructs provider models from the previous Memind-specific configuration, and the old Memind default chat/embedding model properties were removed. Applications must provide Spring-managed ChatModel/EmbeddingModel beans or configure models through spring.ai.chat-models, spring.ai.embedding-models, and spring.ai.model.*. Slot routing remains under memind.ai.chat.slots.
  • The observability integration artifacts changed (feat: migrate observability to Micrometer #134). The old OpenTelemetry tracing plugin/starter and its direct instrumentation path were removed. Replace them with memind-plugin-observability-micrometer or memind-plugin-observability-micrometer-starter, then configure trace export through Micrometer/Spring Boot.
  • Project-owned Jackson APIs migrated to Jackson 3 (chore: migrate project code to Jackson 3 #131). Extensions that directly use exposed JSON types must migrate runtime imports from com.fasterxml.jackson.* to tools.jackson.* where applicable and review removed or changed APIs. Jackson annotations remain the compatibility exception.
  • The managed framework baseline changed ([Feature]: upgrade Spring Boot to 4.1.0 and Spring AI to 2.0.0 #123). The main reactor now targets Spring Boot 4.1 and Spring AI 2.0 GA. Applications importing the Memind BOM should check dependency convergence and compatibility with custom Spring integrations.

Memory and Retrieval

Platform and Integrations

Reliability and Security

Upgrade Checklist

  1. Select the JDBC dialect module required by your database, or retain memind-plugin-jdbc-starter for Spring Boot usage.
  2. Migrate server clients to the standardized response envelope and current synchronous/asynchronous endpoints.
  3. Remove use of the deleted retrieval cache APIs.
  4. Move AI provider/default model configuration to Spring AI properties and verify the required model beans.
  5. Replace the old tracing dependency with the Micrometer observability plugin or starter.
  6. Check Jackson 3 imports/APIs and Spring Boot 4.1/Spring AI 2.0 dependency compatibility.

Full changelog: 0.1.0...0.2.0

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions