Skip to content

fix(deploy): capture migrate stderr so P3005 detection actually works #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
abdout merged 1 commit into from
May 10, 2026
Merged

fix(deploy): capture migrate stderr so P3005 detection actually works #30

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 17 additions & 3 deletions scripts/maybe-migrate.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,8 +38,18 @@ if (!looksReal) {
}

console.log("▶️ Running prisma migrate deploy...");
// Pipe stdout+stderr so we can both inspect them on failure (to detect
// P3005) AND echo them to the parent build log so operators see what
// happened. `stdio: "inherit"` would print directly but leaves
// err.stderr/err.stdout empty on failure, which is why an earlier
// version of this script silently fell through.
try {
execSync("pnpm exec prisma migrate deploy", { stdio: "inherit", encoding: "utf8" });
const out = execSync("pnpm exec prisma migrate deploy 2>&1", {
stdio: ["inherit", "pipe", "pipe"],
encoding: "utf8",
});
// Echo successful output for visibility in build logs.
if (out) process.stdout.write(out);
} catch (err) {
// P3005 = "The database schema is not empty." Happens when the DB was
// populated by `prisma db push` and `_prisma_migrations` is missing or
Expand All @@ -52,9 +62,13 @@ try {
const stdout = (err.stdout ?? "").toString();
const combined = stderr + stdout + (err.message ?? "");

// Always echo the captured output so the operator sees the real error.
if (stdout) process.stdout.write(stdout);
if (stderr) process.stderr.write(stderr);

if (combined.includes("P3005")) {
console.warn(
"⚠️ P3005: production schema is not baselined — skipping migrate deploy.\n" +
"\n⚠️ 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" +
Expand All @@ -63,6 +77,6 @@ try {
process.exit(0);
}

console.error("❌ prisma migrate deploy failed:", err.message);
console.error("\n❌ prisma migrate deploy failed:", err.message);
process.exit(1);
}
Loading