fix(deploy): tolerate P3005 (prod schema not baselined) in build

[abdout]

Hotfix. Unblocks the Vercel deploy pipeline that broke after #25.

What broke

Vercel deploys on main are failing with:

Error: P3005
The database schema is not empty. Read more about how to baseline an
existing production database: https://pris.ly/d/migrate-baseline
❌ prisma migrate deploy failed

This means production was populated via prisma db push or equivalent — the schema exists but _prisma_migrations is empty, so migrate deploy refuses to run pending migrations because it can't tell what's already applied.

Effect

Every push to main since #25 has been blocked. The latest deploy stuck on main is the pre-#28 code, which still has the autocomplete LIMIT == COUNT bug. PRs #19, #22, #23, #24, #26, #27, #28 are all merged on main but not live — Vercel hasn't successfully deployed any commit since #25 went in.

Fix

scripts/maybe-migrate.mjs now catches P3005 specifically, logs an actionable warning with the baseline commands, and exits 0. Other errors still fail the build.

if (combined.includes("P3005")) {
  console.warn(
    "⚠️  P3005: production schema is not baselined — skipping migrate deploy.\n" +
    "    Pending migrations will NOT be applied automatically.\n" +
    "    To baseline (one-time): for each existing migration directory, run\n" +
    "      pnpm exec prisma migrate resolve --applied <migration_name>\n" +
    "    against production DATABASE_URL, then redeploy."
  );
  process.exit(0);
}

Trade-off: pending migrations (the new pg_trgm + listing-indexes ones) don't auto-apply. They land on the database only after a one-time baseline operation. Until then, the new code falls back to its safe paths:

• getLocationSuggestions → try/catch returns [] if pg_trgm missing
• getFullTextMatchingIds → same graceful fallback

After this lands

1. Immediate: prod gets up-to-date code (six PRs' worth) including the count-bug hotfix.
2. Next: a follow-up baseline operation against prod — for each existing migration directory:

   DATABASE_URL='<prod>' pnpm exec prisma migrate resolve --applied 20250720124004_init_with_listing
   # ... repeat for each

   Then a redeploy applies the pending pg_trgm + listing-indexes migrations.

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
mkan	Ready	Preview, Comment	May 10, 2026 6:28am