[BUG]: drizzle-kit migrate: migration SQL failures exit with code 1 but print no error (MigrateProgress hides rejection)

[jakubriedl]

Report hasn't been filed before.

• I have verified that the bug I'm about to report hasn't been filed before.

What version of drizzle-orm are you using?

beta-20

What version of drizzle-kit are you using?

beta-20

Other packages

No response

Describe the Bug

Describe the bug

When drizzle-kit migrate runs against PostgreSQL and a migration fails because of a SQL error (e.g. the database rejects a statement), the CLI process exits with non-zero (e.g. 1) but does not print the underlying error to stdout/stderr. The last thing you see is the animated “applying migrations…” spinner line, so it looks like a silent failure.

Expected behavior

On migration failure, the CLI should print the same error details users need to fix the migration or the database (at minimum: the message from the failed statement / driver error), similar to other commands that surface errors clearly.

Actual behavior

• Exit code is non-zero (failure is detectable in CI).
• No error message is shown; output stops on the spinner line.

How to reproduce

1. Use drizzle-kit with PostgreSQL (pg driver) and a normal drizzle.config.ts pointing at a database.
2. Include a migration whose SQL fails when executed (any intentional SQL error is enough — e.g. a statement that the database rejects).
3. Run drizzle-kit migrate.

Observe: command fails with exit code 1 but no visible error text.

Note: Running the same migrations programmatically via drizzle-orm’s migrate() (e.g. drizzle-orm/node-postgres/migrator) does surface the error, which confirms the failure is real and only the CLI output path is wrong.

Environment

• OS: (any; observed on macOS)
• drizzle-kit: (beta / version in use)
• drizzle-orm: (beta / version in use)
• Driver: pg / PostgreSQL

Possible cause (for maintainers)

In the bundled CLI, TaskTerminal.reject(err) calls view.render("rejected", err), but MigrateProgress.render appears to only accept status and treats "rejected" the same as "pending" (spinner only), without using the err argument. Other progress views (e.g. introspection) include a branch that prints error.message when status === "rejected".

If that’s accurate, the fix would be to extend MigrateProgress to render the error on rejection, consistent with those other views.

Additional context

This makes debugging failed migrations unnecessarily difficult in local and CI environments because users must bypass the CLI or add wrappers to see the real database error.

[balloman]

Can confirm I'm also experiencing this issue, making it very hard to debug

[MarZab]

If we can assume this will be the last message of the view, then the fix would be to simply return the error

MarZab@1616eee

[tomislavcivcija]

Having the same issue,

npx drizzle-kit migrate
No config path provided, using default 'drizzle.config.ts'
Reading config file '/app/drizzle.config.ts'
Using 'pg' driver for database querying

fails silently with exit code 1

The versions I'm using

npx drizzle-kit --version
drizzle-kit: v0.31.10
drizzle-orm: v0.45.2 

Rollback to drizzle-kit: v0.31.9 fixes the issue.

[mhornbacher]

We cannot rollback as we are on the beta and the migration format changed as well there...

Is the team open to us fixing this issue upstream?

[ragavan-r-r]

yes i have this issue as well, even when i try pushing to the database the same thing happens...

[cvienna]

I'm self-hosting PostgreSQL with Docker. Drizzle suppresses SQL errors in the terminal, which makes debugging really annoying. I found the actual errors in Docker Desktop's logs — check there, or wherever you can access your Postgres logs.

In my case it turned out to be a type mismatch between two columns. Once I fixed that, migrations worked fine. The root cause will be specific to your codebase, but the key thing is: don't trust the Drizzle error output, find your Postgres logs.

[itsalb3rt]

I'm self-hosting PostgreSQL with Docker. Drizzle suppresses SQL errors in the terminal, which makes debugging really annoying. I found the actual errors in Docker Desktop's logs — check there, or wherever you can access your Postgres logs.

In my case it turned out to be a type mismatch between two columns. Once I fixed that, migrations worked fine. The root cause will be specific to your codebase, but the key thing is: don't trust the Drizzle error output, find your Postgres logs.

Thanks! In my case, apparently the Drizzle doesn't run any query, now I have an idea to continue testing

[AndriiSherman]

Should be fix in drizzle-orm@1.0.0-beta.22 and drizzle-kit@1.0.0-beta.22