Marco Beretta ce240d8b3b fix: cap shared-link expiry at source conversation and enforce retention on assistant saves ... getSharedLinkExpiration starts a brand-new retention window when the source conversation still has an active expiration, letting a share outlive the conversation whose messages it embeds. Cap the share at the earlier of the source expiration and a freshly created window, and fall back to the source expiration when window creation fails. The Assistants chat path saved messages via recordMessage, which bypasses retention, while saveConvo forced the conversation temporary. In ephemeral mode the conversation expired but its messages persisted with no expiredAt. Route saveUserMessage, saveAssistantMessage and syncMessages through saveMessage so messages inherit the same forced retention as the conversation.		2026-06-30 04:51:45 +02:00
..
index.js	✨ feat: Assistants API, General File Support, Side Panel, File Explorer (#1696)	2024-02-13 20:42:27 -05:00
manage.js	fix: cap shared-link expiry at source conversation and enforce retention on assistant saves	2026-06-30 04:51:45 +02:00
manage.retention.spec.js	fix: cap shared-link expiry at source conversation and enforce retention on assistant saves	2026-06-30 04:51:45 +02:00
processMessages.spec.js	🔧 chore: Update ESLint Config & Run Linter (#10986)	2025-12-15 17:55:25 -05:00