mirror of
https://github.com/danny-avila/LibreChat.git
synced 2026-11-19 22:43:38 +00:00
* fix: Stop Cache Audit From Logging Cache Keys and Values * fix: Keep Cache Audit Output to Counts and TTL * fix: Log Cache Audit at Info So the Debug Toggle Still Emits * test: Cover Cache Audit Redaction in the Mock Lane * test: Run Cache Audit Scenario Against In-Memory Stores * test: Parse Cache Audit Probe Output Before Asserting * fix: Render Cache Audit Statistics in the Message and Move Formatting to packages/api * fix: Encrypt User Plugin Credentials With Random-IV v3 Format * test: Cover Credential Encryption Formats in Mock E2E Scenarios * test: Round-Trip Real Credential Helpers in PluginService Spec * 🙈 fix: Remove SharePoint Picker Payload Logging (#16997) * fix: Add credentials.writeFormat to Gate v3 Credential Writes During Rollouts * test: Expect 201 When the Legacy Write Format Override Is Created * fix: Clear TTS Audio Cache On Session End and Hash Its Keys * fix: Read Manual TTS Replays From the Hashed Cache Key * fix: Purge Legacy TTS Cache Keys and Fence Writes Across Logout * fix: Keep TTS Cache Writes Off the Playback Path * test: Expect Hashed Keys in the StreamAudio Cache Lookup * test: Use a Single-Token Reply Label in the TTS Cache Scenario * fix: Settle TTS Cache Clear Before IdP Logout and Across Tabs * test: Cover the TTS Cache Fence When Another Tab Logs Out * test: Wait for the Second Tab Before Logging Out in the TTS Scenario * fix: Latch TTS Cache Writes Shut Until the Tab Authenticates Again * fix: Reopen TTS Cache Writes When Authentication Completes In Place * fix: Leave for the IdP Even When TTS Cache Cleanup Fails * fix: Retry a Failed Legacy TTS Purge and Fence Other Tabs on Manual Clear * fix: Rerun the Legacy TTS Purge After Each Clear and Sign-In * fix: Rerun the Legacy TTS Purge When Another Tab Clears * fix: Fence Pre-Auth TTS Writes, Retry Failed Clears, and Fall Back to Storage Events * fix: Version the Hashed TTS Cache Key Path * fix: Move TTS Audio to a New Cache and Keep It Closed Until a Failed Clear Succeeds * fix: Persist a Pending TTS Cache Delete Across Navigation * fix: Reopen TTS Caching Only on Session Start and Fence Cache Reads * fix: Keep the TTS Delete Fence in Cache Storage and Close Reads After Logout * refactor: Keep Read-Aloud Audio in Tab Memory Instead of Cache Storage * test: Return to the Conversation After Re-Login in the TTS Logout Scenario * test: Close the Phone Sidebar Before Replaying in the TTS Logout Scenario * fix: Bound the In-Memory TTS Cache by Size as Well as Count * fix: Scope Cached TTS Audio to the Signed-In User * fix: Keep the Settings Cache Delete Available While Legacy Audio Remains * fix: Recheck Legacy TTS Audio After a Settings Clear and on Unowned Handoff * fix: Fence TTS Writes Started Before an Account Signs In * test: Opt the Fresh TTS Account Into Enter-to-Send * fix: Load Google Tag Manager Only After Analytics Consent Google Tag Manager initialized as soon as the chat footer or the chat route mounted whenever ANALYTICS_GTM_ID was set, for signed-in users and shared-link viewers alike, with no consent check. A single useAnalytics hook now owns initialization and loads the container only after the viewer grants consent, recorded in a persisted Jotai atom. A non-modal banner asks for that consent in the signed-in layout and on shared links, and a Data controls toggle changes it later; withdrawing consent pushes a consent mode update to a loaded container and completes on reload. * fix: Restore Analytics Consent to a Container Still on the Page * test: Cover Analytics Consent Scenarios * test: Observe Missing Tag Manager Requests Over a Bounded Window * fix: Recognize Only the Configured Tag Manager Container * fix: Send Consent Withdrawal Only to the Configured Container * fix: Describe the Consent Withdrawal Guard Accurately * fix: Keep Advertising Consent Denied When Analytics Is Allowed * fix: Let Shared-Link Viewers Change Analytics Consent * fix: Retry a Tag Manager Container That Never Registered * fix: Treat a Loading Container as Present and Drop It When It Fails * fix: Drop a Failed Tag Manager Attempt's Start Event Before Retrying
16 lines
632 B
TypeScript
16 lines
632 B
TypeScript
import { createStorageAtom } from './jotai-utils';
|
|
|
|
export type AnalyticsConsent = 'granted' | 'denied';
|
|
|
|
/** The viewer's answer to the analytics consent banner. `null` means they have
|
|
* not answered yet, which counts as no consent: Google Tag Manager loads only
|
|
* after an explicit `granted`. */
|
|
export const analyticsConsentAtom = createStorageAtom<AnalyticsConsent | null>(
|
|
'analyticsConsent',
|
|
null,
|
|
);
|
|
|
|
/** Whether the deployment configured Google Tag Manager at all. */
|
|
export function hasAnalyticsGtmId(gtmId: string | null | undefined): gtmId is string {
|
|
return typeof gtmId === 'string' && gtmId.trim() !== '';
|
|
}
|