Prisma migrate dev hangs without TTY input
- Investigating(current)
- Trending(upcoming)
- Workaround available(upcoming)
- Resolved(upcoming)
Executive summary
The `prisma migrate dev` command hangs when stdin is not a terminal, requiring the user to manually enter a migration name. This issue affects users who run the command in scripts or coding agents where stdin is not a TTY.
No verified workaround yet
None of the linked reports describe a mitigation. Follow this incident to hear when one appears.
Under active investigation. No report has identified a root cause yet.
Evidence
1 report · 1 GitHubShow
- [1]GitHub First report`migrate dev` hangs on the migration name prompt when stdin is not a TTY(opens GitHub issue in a new tab)
Package and version prisma@7.10.1 What happened? prisma migrate dev without --name hangs forever on "Enter a name for the new migration:" when stdin is not a terminal (e.g. if it's a script or a coding agent). What did you expect to happen? The prompt should be skipped and the migration created with the default empty name, same as when CI=1 is set. Minimal reproduction Repro in arbitrary project If you already have a Prisma project at hand, just change the schema to trigger a migration and…
by sodic 0upvotes 1comments
Timeline
- First report on GitHub issue
`migrate dev` hangs on the migration name prompt when stdin is not a TTY
Source