The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 23, 2026 6:34am

@BugBot review

PR Summary

Medium Risk
Moderate risk due to a schema migration that moves retention configuration from workspace columns to organization.data_retention_settings, plus updated cleanup dispatch logic that could change what gets deleted across all workspaces in an org.

Overview
Switches Enterprise data retention from per-workspace to organization-wide. Retention settings are now stored on organization.data_retention_settings (JSON) and the per-workspace retention columns are dropped via migration.

Adds a new org-scoped API at GET/PUT /api/organizations/[id]/data-retention with member read access and owner/admin write access (including audit logging), and updates the EE settings UI + React Query hooks to read/update org settings instead of workspace settings.

Updates cleanup job dispatching to resolve enterprise retention from the owning organization’s settings, and fixes log cleanup to also purge job_execution_logs in addition to workflow_execution_logs (with updated logging).

^{Reviewed by Cursor Bugbot for commit 39bb125. Bugbot is set up for automated code reviews on this repo. Configure here.}

@BugBot review

@BugBot review

Greptile Summary

This PR moves data retention configuration from the workspace level to the organization level, replacing three integer columns on workspace with a single dataRetentionSettings JSON column on organization. It also fixes a bug where jobExecutionLogs (mothership-ran workflow logs) were not being cleaned up alongside workflowExecutionLogs.

• The SQL migration drops the three per-workspace retention columns without a preceding UPDATE to copy any existing values into organization.data_retention_settings, so any enterprise workspace that already had retention configured will lose those settings silently when the migration runs.

Confidence Score: 4/5

Safe to merge after confirming no production enterprise workspaces have existing per-workspace retention values configured, or after adding a data migration step.

One P1 concern: the migration irreversibly drops three workspace retention columns without migrating existing data. If any enterprise workspace has these set in production, those settings are permanently lost. The rest of the PR is well-structured with correct auth checks, proper cache invalidation, and a clean bug fix for job execution log cleanup.

packages/db/migrations/0196_retention_org_level.sql — needs a data migration step before the DROP COLUMN statements.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[dispatchCleanupJobs] --> B{Plan type?}
    B -->|free/pro/team| C[resolveWorkspaceIdsForPlan]
    B -->|enterprise| D[Query workspaces\nINNER JOIN organization\nINNER JOIN subscription\nWHERE org.dataRetentionSettings->>key IS NOT NULL]
    C --> E[Enqueue cleanup job\nplan payload]
    D --> F[Enqueue cleanup job\nworkspaceId payload]
    E --> G[resolveCleanupScope]
    F --> G
    G -->|plan payload| H[Use CLEANUP_CONFIG defaults]
    G -->|enterprise payload| I[JOIN workspace → organization\nRead settings->>key]
    H --> J[runCleanupLogs]
    I --> J
    J --> K[cleanupTier\nworkflow_execution_logs]
    J --> L[cleanupJobExecutionLogsTier\njob_execution_logs]

_{Reviews (1): Last reviewed commit: "Merge remote-tracking branch 'origin/sta..." | Re-trigger Greptile}