{"version":"2.1.223","anchor":"memory-api-entry-schema-accepts-size-bytes-and-updated-at","canonical_anchor":"memory-api-entry-schema-accepts-size-bytes-and-updated-at","heading":"Memory-API entry schema accepts size_bytes and updated_at","tier":"internal","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/memory-api-entry-schema-accepts-size-bytes-and-updated-at","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Memory-API entry schema accepts size_bytes and updated_at\n\nMemory entries with size and update-time fields from newer servers no longer break parsing.\n\n**What**\n\nMemory entry payloads from newer servers parse without error.\n\n**Details**\n\n- The schema gained an optional non-negative integer `size_bytes` alongside the existing `content_size_bytes`.\n- It also gained an optional `updated_at` string that falls back to undefined via `.catch(void 0)` rather than failing the parse.\n\n**Evidence**\n\n`size_bytes: w.number().int().nonnegative().optional(),`\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}