From 47a69e1e72dc562b6fdd49a9ef892229afc7508a Mon Sep 17 00:00:00 2001 From: Kartik Date: Thu, 24 Sep 2026 00:30:19 +0530 Subject: [PATCH] docs(changelog): add v2.2.1 entry for Valkey None-timestamps fix (#7425) --- docs/changelog/sdk.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/changelog/sdk.mdx b/docs/changelog/sdk.mdx index bf53c5d31..3f4a64202 100644 --- a/docs/changelog/sdk.mdx +++ b/docs/changelog/sdk.mdx @@ -12,6 +12,9 @@ mode: "wide" **New Features:** - **Client:** Add User Profiles to `MemoryClient` and `AsyncMemoryClient`: `get_profile()`, `generate_profile()`, `get_profile_settings()`, `update_profile_settings()`, `sample_profiles()`, and `get_profile_job()`. A profile is a structured, always-current JSON summary of one user, shaped by a JSON Schema you configure per project and filled by an LLM from that user's memories. Generation is asynchronous. Every job POST carries an `Idempotency-Key`; to retry a lost request without starting a second job, pass the same `idempotency_key` on each attempt ([#7340](https://github.com/mem0ai/mem0/pull/7340)) +**Bug Fixes:** +- **Vector Stores:** Guard against `None` timestamps in the Valkey vector store's `insert()` and `update()` paths. `created_at` and `updated_at` fields that were present in the payload but set to `None` previously passed the `"created_at" not in payload` / `"updated_at" in payload` checks and raised `TypeError` when `datetime.fromisoformat()` received `None`. Both paths now use `.get()` with a truthiness check so `None` values fall through to the default, matching the Redis provider's behavior ([#6993](https://github.com/mem0ai/mem0/pull/6993)) +