Marco Beretta fd8292669d fix: only cap message expiry to the parent on message-only saves ... Capping every forced message save to the parent expiry broke the normal send paths: POST /api/messages/:conversationId and BaseClient.saveMessageToDatabase call saveConvo right after saveMessage, refreshing the conversation to a fresh TTL. The message kept the older parent deadline, so the message TTL index could delete the just-sent message while the conversation stayed visible until the later deadline. Gate the cap behind a capExpiryToConversation flag that only the message-only callers (branch, artifact, abort) set, since those never run saveConvo. Normal sends leave the message on its fresh deadline, which the following saveConvo refresh keeps aligned. The conversion/re-cap cascade still runs for every forced save.		2026-06-23 16:41:33 +02:00
..
api	fix: cap shared-link expiry at source conversation and enforce retention on assistant saves	2026-06-23 16:40:57 +02:00
client	🏷️ chore: Bump Individual Package Versions (#13891)	2026-06-22 09:54:19 -04:00
data-provider	feat: add ephemeral retention mode for forced temporary chats	2026-06-23 16:40:21 +02:00
data-schemas	fix: only cap message expiry to the parent on message-only saves	2026-06-23 16:41:33 +02:00