Skip to content

CHANGELOG.md

Latest commit

 

History

History
55 lines (41 loc) · 7.49 KB

CHANGELOG.md

File metadata and controls

55 lines (41 loc) · 7.49 KB

Changelog

All notable changes to atomicmemory will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[1.1.1] - 2026-06-11

Added

  • UnsupportedOperationError (subclass of ProviderError) and InvalidScopeError (subclass of ValidationError), raised where those parents were previously raised bare: a provider missing the package extension, and an operation missing required scope fields. Existing except ProviderError / except ValidationError handlers keep working; consumers can now catch the specific types, matching the TS SDK. Exported from the package root.
  • AsyncMemoryProcessingPipeline + NOOP_ASYNC_PIPELINE (exported from atomicmemory.memory alongside the existing sync type): the async-surface pipeline type used by AsyncProviderRegistration.
  • EntitiesClient / AsyncEntitiesClient: the entities namespace over /v1/entities, ported from the TS SDK — entity profiles, listing, detail, cascade delete, attribute triples, per-memory history, per-entity settings patching, and entity merge. Wired into AtomicMemoryClient/AsyncAtomicMemoryClient as .entities on the same transport config, closed with the client. Python field names match the snake_case wire directly (the TS camelCase mapping layer has no Python counterpart).

Changed

  • Registered memory pipelines now actually execute: MemoryService/AsyncMemoryService run preprocess_ingest (which may split one input into many; per-item results merge in order), postprocess_ingest, preprocess_search/postprocess_search (postprocess receives the processed request), preprocess_get/postprocess_get, and postprocess_list, matching the TS MemoryService semantics. delete and package take no pipeline. Before 1.1.1 these hooks were accepted at registration but never invoked. Hook exceptions propagate unwrapped — hooks are caller-supplied code.
  • MemoryProcessingPipeline hook signatures are now synchronous (the async surface uses AsyncMemoryProcessingPipeline). Type-hint change only for code that constructed pipelines — which received no behavior before this release.

[1.1.0] - 2026-06-09

Added

  • atomicmemory.contract.v1: a wire codec for the v1 provider contract's deliberately mixed-case encoding (Memory.createdAt/updatedAt and SearchResult.rankingScore are camelCase on the wire; version_id, observed_at, and retrieval-receipt fields are snake_case). Encode/decode helpers cover Memory, Provenance, SearchResult, SearchResultPage, SearchRequest, and ingest payloads (IngestInput, IngestResult). Dates follow the contract's ISO-8601 UTC millisecond Z form (_to_iso_z, equivalent to TS toISOString()). Naive datetimes in encode paths are assumed UTC. encode_ingest_input fails closed on the Python-ahead content_class field (no place in the v1 additionalProperties: false schemas; TS contract alignment is a recorded follow-up). Explicit-null version_id in SearchResult normalizes to absent on re-encode, matching the TS optional declaration. encode_search_request uses by_alias=True so Python-keyword-safe combinator field names (and_/or_/not_) emit their wire aliases; a recursive _jsonify walk converts any datetime operands in filter trees to the toISOString form. In-process models and provider mappers are unchanged.
  • Vendored the TS SDK's versioned v1 wire contract (JSON Schemas, cross-provider conformance corpus, and CONTRACT.md) under contract/, with explicit provenance in contract/VENDORED.json and a documented refresh script (scripts/refresh_contract.py, never run in CI). A pytest conformance harness proves corpus fixtures decode into the Python models (directly for snake-on-wire types, through the codec for the mixed-case search response) and that SDK emissions validate against the vendored draft-2020-12 schemas, with the TS suite's negative cases mirrored against both schemas and Pydantic. The capabilities-descriptor case is schema-only (no Python model in this release — recorded follow-up).
  • atomicmemory.contract re-exports v1 as a specialty import surface; deliberately not re-exported from the package root to keep the root namespace focused on the core provider API.
  • AsyncProviderFactory now accepts factories that return an Awaitable[AsyncProviderRegistration], enabling lazy or async provider construction during AsyncMemoryService.initialize().
  • MemoryService.initialize() and AsyncMemoryService.initialize() raise ConfigError when the configured default provider has no registered factory, making a misconfigured default an immediate, explicit error rather than a silent no-op.

Changed

  • content_class is now accepted on every ingest mode (text, messages, and verbatim), not just verbatim, and is forwarded to core for all modes. Extraction-based ingests (text/messages) can now satisfy a core running the default RAW_CONTENT_POLICY=reject. Still never defaulted — omitting it leaves the field off the wire and a reject-policy core fails closed.
  • Both clients' initialize() is now concurrency-safe and idempotent: concurrent callers share a single initialization run (the first caller's registry wins), and the completed outcome — success or failure — is captured in loop-independent state for AsyncMemoryClient.
  • A failed initialize() is sticky: retrying re-raises the original error from any caller; resolve the cause and construct a new client rather than retrying on the same instance.
  • AsyncMemoryClient.initialize() shields each waiter from cancellation so that one waiter's timeout or cancellation never cancels the shared run for other concurrent callers.
  • AsyncMemoryClient.close() during a pending initialization cancels the shared run; staged providers are torn down by the service's atomic-initialize cleanup, any concurrent initialize() waiter receives CancelledError, and the client ends in the not-initialized state without recording a sticky error.
  • Both MemoryService and AsyncMemoryService stage provider registrations atomically: factories and provider initialize() calls run against a local staging area, and the maps are replaced only after every provider succeeds; on any failure, already-staged providers are torn down best-effort before the original error re-raises.
  • MemoryService.close() and AsyncMemoryService.close() are best-effort: every provider gets a chance to close regardless of earlier failures, maps are cleared in a finally block, and the first failure is re-raised after all providers have been given the chance to close.

Fixed

  • atomicmemory.__version__ reported 1.0.0 while package metadata said 1.0.1; all version sources now agree at 1.1.0, guarded by a regression test that will fail if they drift again.

[1.0.1] - 2026-05-14

Changed

  • Version bump for public package publication after internal-to-public repository sync.

[1.0.0]

Initial public stable release.

Added

  • AtomicMemoryClient and AsyncAtomicMemoryClient as the primary public client surfaces.
  • Memory ingestion, search, package, get, list, and delete support.
  • AtomicMemory, Mem0, and Hindsight provider adapters.
  • Typed AtomicMemory namespace handles for lifecycle, audit, lessons, agents, and runtime config.
  • Direct artifact storage client with pointer and managed artifact workflows.
  • Local embedding, semantic search, and KV cache helpers.
  • Pydantic models, typed exceptions, and py.typed marker for downstream type checkers.