fix(db): allow five hours for database migrations

[icecrasher321]

Summary

• Increase the database migration job timeout from 180 to 300 minutes so bulk projection backfills and concurrent index builds have time to finish on larger databases.

Type of Change

• Bug fix

Testing

• Parsed the workflow YAML and verified the 300-minute job timeout applies to both workflow entry points.
• Repository lint, all repository audits (including strict API validation), block registry validation, and docs manifest validation passed.
• Regenerated committed artifacts with no additional changes.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing — configuration-only change; validated the workflow directly.
• 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.

Project	Deployment	Actions	Updated
docs	Building	Preview	Sep 15, 2026 1:46am UTC

[icecrasher321]

@greptile

[icecrasher321]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

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

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge.

Summary

Increases the database migration job timeout from three hours to five hours so long-running backfills and concurrent index builds can complete.

• Applies the 300-minute timeout to the shared migration job used by callable and manually dispatched workflows.
• Does not change migration commands, credentials, triggers, or database behavior.

_{Reviews (1) · Last reviewed commit: "fix(db): allow five hours for database m..."}