improvement(db): finish workspace file size cutover

[waleedlatif1]

Summary

• Backfill workspace_files.size_bytes in bounded, resumable batches and keep old/new writers compatible during rollout
• Cut application reads and writes over to the canonical bigint size column
• Leave the legacy int4 column behind a contract marker for removal after this release is fully deployed

Type of Change

• Improvement

Testing

Tested with lint, the full audit suite, migration safety checks, app/database type-checks, targeted app and migration tests, and an isolated PostgreSQL 17 migration run.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 26, 2026 7:18pm

[waleedlatif1]

@greptile

[greptile-apps]

Greptile Summary

The PR completes the workspace-file size cutover from the legacy integer field to the canonical bigint field.

• Adds compatible rollout SQL, a bounded resumable backfill, and a dev-specific cutover path.
• Moves application storage accounting, copying, cleanup, metadata, and quota paths to size_bytes.
• Retains the legacy column and synchronization trigger for rolling-deployment compatibility.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
packages/db/migrations/0308_workspace_file_size_cutover.sql	Adds rolling-deployment compatibility between the legacy integer size and canonical bigint size.
packages/db/script-migrations/0008_backfill_workspace_file_size_bytes.ts	Implements an idempotent, keyset-paginated backfill with independently committed batches.
packages/db/scripts/apply-dev-workspace-file-size-cutover.ts	Applies compatibility SQL and the canonical-size backfill to existing dev databases before recording completion.
.github/workflows/migrations.yml	Runs the temporary cutover after the dev schema push.
packages/db/schema.ts	Makes size_bytes the canonical application field while retaining the legacy size column for rollout compatibility.
apps/sim/lib/billing/storage/payer-transfer.ts	Recomputes payer-transfer storage totals from the canonical bigint size column.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Apply schema changes] --> B[Install size synchronization trigger]
  B --> C[Backfill null size_bytes rows in bounded batches]
  C --> D[Record script migration completion]
  D --> E[Deploy canonical size_bytes readers and writers]
  E --> F[Remove compatibility artifacts after rollout]

Loading

_{Reviews (4): Last reviewed commit: "fix(db): fail closed on missing file siz..." | Re-trigger Greptile}

[cubic-dev-ai]

All reported issues were addressed

<sub>Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic review

[waleedlatif1]

@greptile

[cubic-dev-ai]

@cubic review

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

[cubic-dev-ai]

No issues found across 35 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Re-trigger cubic</sub>