TinaCMS Schema Sync

Regenerate TinaCMS artifacts locally and commit them after schema changes. This handles the hybrid deployment strategy where tinacms build is skipped on Vercel and artifacts are pre-committed.

When to Use

• After editing tina/config.ts (adding fields, blocks, collections)
• After upgrading @tinacms/cli
• When pnpm tina:build fails with "Unable to seed" (content references unknown block types)
• When Vercel deploys succeed but new blocks don't render

Prerequisites

• TinaCloud credentials in .env.local:

  NEXT_PUBLIC_TINA_CLIENT_ID="..."
  TINA_TOKEN="..."
  

• If .env.local doesn't exist, run ./scripts/pull-secrets.sh or copy from .env.example and fill in values from TinaCloud dashboard.