feat: add calendar cache status and actions (#22532)

[ShashankFC]

Test 1rnnn

Summary by CodeRabbit

• New Features

  • Added cache management capabilities for integrations, including ability to view cache status with last updated timestamp and delete cached data.

• Documentation

  • Added localization strings for cache management UI elements.

• Chores

  • Updated development tooling for cron job execution.
  • Added setup script for Google Cloud webhook configuration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

nn---n*Replicated from [ai-code-review-evaluation/cal.com-coderabbit#11](https://github.com/ai-code-review-evaluation/cal.com-coderabbit/pull/11)*

[ShashankFC]

@cubic-dev-ai review this pull request

[cubic-dev-ai]

@cubic-dev-ai review this pull request

@ShashankFC I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

5 issues found across 17 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="packages/app-store/googlecalendar/lib/CalendarService.ts">

<violation number="1" location="packages/app-store/googlecalendar/lib/CalendarService.ts:1024">
P1: Bug: Passing empty `{}` to `updateMany` will not trigger `@updatedAt` — this is a no-op. Prisma's `@updatedAt` only updates the timestamp when at least one field is actually changed. You need to explicitly set the timestamp.</violation>
</file>

<file name="scripts/test-gcal-webhooks.sh">

<violation number="1" location="scripts/test-gcal-webhooks.sh:68">
P2: `sed -i ''` is macOS/BSD-specific. On GNU/Linux, this fails because `-i` expects the extension as a suffix to the flag (e.g., `sed -i''`) or uses `-i` alone for no-backup in-place editing. Consider a portable alternative.</violation>
</file>

<file name="packages/trpc/server/routers/viewer/calendars/connectedCalendars.handler.ts">

<violation number="1" location="packages/trpc/server/routers/viewer/calendars/connectedCalendars.handler.ts:29">
P1: Missing error handling: if `getCacheStatusByCredentialIds` throws, the entire connected calendars endpoint fails. Cache status is supplementary data — a failure here should not prevent users from seeing their calendars. Wrap the cache lookup in a try/catch and fall back gracefully.</violation>
</file>

<file name="apps/web/package.json">

<violation number="1" location="apps/web/package.json:11">
P2: `tsx` is not a declared dependency — `npx tsx` will download an unpinned version on each first run, making builds non-deterministic. Additionally, `ts-node` is already a devDependency and is still used by other scripts (`check-changed-files`, `translate-locales`). Either add `tsx` to `devDependencies` with a pinned version, or keep using the already-installed `ts-node`.</violation>
</file>

<file name="packages/features/apps/components/CredentialActionsDropdown.tsx">

<violation number="1" location="packages/features/apps/components/CredentialActionsDropdown.tsx:89">
P2: The date formatter hardcodes `"en-US"` locale instead of using the user's current locale from the `i18n` instance already available via `useLocale()`. This means all users will see US-formatted dates regardless of their language setting.

Use `i18n.language` (or derive a proper locale from it) to format dates according to the user's preferences.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P1: Bug: Passing empty {} to updateMany will not trigger @updatedAt — this is a no-op. Prisma's @updatedAt only updates the timestamp when at least one field is actually changed. You need to explicitly set the timestamp.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At packages/app-store/googlecalendar/lib/CalendarService.ts, line 1024:

<comment>Bug: Passing empty `{}` to `updateMany` will not trigger `@updatedAt` — this is a no-op. Prisma's `@updatedAt` only updates the timestamp when at least one field is actually changed. You need to explicitly set the timestamp.</comment>

<file context>
@@ -1019,6 +1019,9 @@ export default class GoogleCalendarService implements Calendar {
     }
+
+    // Update SelectedCalendar.updatedAt for all calendars under this credential
+    await SelectedCalendarRepository.updateManyByCredentialId(this.credential.id, {});
   }
 
</file context>

Suggested change

	await SelectedCalendarRepository.updateManyByCredentialId(this.credential.id, {});
	await SelectedCalendarRepository.updateManyByCredentialId(this.credential.id, { updatedAt: new Date() });

[cubic-dev-ai]

P1: Missing error handling: if getCacheStatusByCredentialIds throws, the entire connected calendars endpoint fails. Cache status is supplementary data — a failure here should not prevent users from seeing their calendars. Wrap the cache lookup in a try/catch and fall back gracefully.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At packages/trpc/server/routers/viewer/calendars/connectedCalendars.handler.ts, line 29:

<comment>Missing error handling: if `getCacheStatusByCredentialIds` throws, the entire connected calendars endpoint fails. Cache status is supplementary data — a failure here should not prevent users from seeing their calendars. Wrap the cache lookup in a try/catch and fall back gracefully.</comment>

<file context>
@@ -23,8 +24,19 @@ export const connectedCalendarsHandler = async ({ ctx, input }: ConnectedCalenda
 
+  const credentialIds = connectedCalendars.map((cal) => cal.credentialId);
+  const cacheRepository = new CalendarCacheRepository();
+  const cacheStatuses = await cacheRepository.getCacheStatusByCredentialIds(credentialIds);
+
+  const cacheStatusMap = new Map(cacheStatuses.map((cache) => [cache.credentialId, cache.updatedAt]));
</file context>

[cubic-dev-ai]

P2: sed -i '' is macOS/BSD-specific. On GNU/Linux, this fails because -i expects the extension as a suffix to the flag (e.g., sed -i'') or uses -i alone for no-backup in-place editing. Consider a portable alternative.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At scripts/test-gcal-webhooks.sh, line 68:

<comment>`sed -i ''` is macOS/BSD-specific. On GNU/Linux, this fails because `-i` expects the extension as a suffix to the flag (e.g., `sed -i''`) or uses `-i` alone for no-backup in-place editing. Consider a portable alternative.</comment>

<file context>
@@ -0,0 +1,79 @@
+fi
+
+if grep -q '^GOOGLE_WEBHOOK_URL=' "$ENV_FILE"; then
+  sed -i '' -E "s|^GOOGLE_WEBHOOK_URL=.*|GOOGLE_WEBHOOK_URL=$TUNNEL_URL|" "$ENV_FILE"
+else
+  echo "GOOGLE_WEBHOOK_URL=$TUNNEL_URL" >> "$ENV_FILE"
</file context>

[cubic-dev-ai]

P2: tsx is not a declared dependency — npx tsx will download an unpinned version on each first run, making builds non-deterministic. Additionally, ts-node is already a devDependency and is still used by other scripts (check-changed-files, translate-locales). Either add tsx to devDependencies with a pinned version, or keep using the already-installed ts-node.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At apps/web/package.json, line 11:

<comment>`tsx` is not a declared dependency — `npx tsx` will download an unpinned version on each first run, making builds non-deterministic. Additionally, `ts-node` is already a devDependency and is still used by other scripts (`check-changed-files`, `translate-locales`). Either add `tsx` to `devDependencies` with a pinned version, or keep using the already-installed `ts-node`.</comment>

<file context>
@@ -8,7 +8,7 @@
     "clean": "rm -rf .turbo && rm -rf node_modules && rm -rf .next",
     "dev": "yarn copy-static && next dev --turbopack",
-    "dev:cron": "ts-node cron-tester.ts",
+    "dev:cron": "npx tsx cron-tester.ts",
     "dev-https": "NODE_TLS_REJECT_UNAUTHORIZED=0 next dev --experimental-https",
     "dx": "yarn dev",
</file context>

Suggested change

	"dev:cron": "npx tsx cron-tester.ts",
	"dev:cron": "ts-node cron-tester.ts",

[cubic-dev-ai]

P2: The date formatter hardcodes "en-US" locale instead of using the user's current locale from the i18n instance already available via useLocale(). This means all users will see US-formatted dates regardless of their language setting.

Use i18n.language (or derive a proper locale from it) to format dates according to the user's preferences.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At packages/features/apps/components/CredentialActionsDropdown.tsx, line 89:

<comment>The date formatter hardcodes `"en-US"` locale instead of using the user's current locale from the `i18n` instance already available via `useLocale()`. This means all users will see US-formatted dates regardless of their language setting.

Use `i18n.language` (or derive a proper locale from it) to format dates according to the user's preferences.</comment>

<file context>
@@ -0,0 +1,157 @@
+                  <div className="text-sm font-medium text-gray-900 dark:text-white">{t("cache_status")}</div>
+                  <div className="text-xs text-gray-500 dark:text-white">
+                    {t("cache_last_updated", {
+                      timestamp: new Intl.DateTimeFormat("en-US", {
+                        dateStyle: "short",
+                        timeStyle: "short",
</file context>