Summary
This PR fixes #5601 #5521 #3214; issues where database migrations could fail silently without surfacing errors, making debugging difficult and misleading for users.

Previously, when running migrations generated by npx drizzle-kit generate, any runtime errors during execution were not properly surfaced. This resulted in migrations appearing to succeed even when they had actually failed at the database execution layer.

This behavior occurs regardless of SQL dialect and is for example problematic when generated SQL is incompatible with the target database (e.g. MySQL constraints such as UUID vs CUID mismatches).

Changes

• Introduced a connection context wrapper in drizzle-kit/src/cli/connections.ts ensures migration execution context is properly tracked
• Captures and reports runtime errors instead of swallowing them
• Improved error propagation so failures during migration execution are no longer silent

Test coverage

A new test scenario was added in drizzle-kit/tests/cli-migrate.test.ts
This validates a case where:

• A schema is generated using npx drizzle-kit generate
• The schema includes an unsupported type (e.g. CUID in MySQL context where only UUID is valid)
• Migration execution via npx drizzle-kit migrate correctly fails with a visible error message