db push applies migrations when the confirmation answer is not yes or no
Los mantenedores suelen responder en 1 día
@7ttp ya está trabajando en esto.
Desde el 28/9/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Affected area
Migrations
Supabase CLI version
2.107.0 (Homebrew). The CLI also reported that 2.118.0 is available.
Operating system
macOS (darwin 25.6.0, arm64)
Installation method
brew (/opt/homebrew/bin/supabase, package [email protected])
Command
supabase db push
At the confirmation prompt the answer entered was u, then Enter. That is not y or n.
Actual output
Do you want to push these migrations to the remote database?
• <pending-migration>.sql
[Y/n] u
Applying migration <pending-migration>.sql...
Finished supabase db push.
A second supabase db push then reported Remote database is up to date. The migration had been applied.
Expected behavior
[Y/n] means Enter, y, and yes confirm, and n and no decline. Any other non-empty answer should be rejected.
On an interactive terminal the prompt should say the answer was not recognized and ask again. It should not apply migrations. When stdin is not a terminal, a non-empty unrecognized answer should fail the command instead of taking the default. An empty line can still take the default, which is what Enter means.
Steps to reproduce
- Use Supabase CLI 2.107.0, linked to a remote project that has at least one pending migration.
--dry-runshows the same prompt path without writing. - Run
supabase db push. - At
[Y/n], typeuand press Enter. - The pending migration is applied.
The same parser is what makes printf 'u\n' dangerous anywhere this prompt reads a line and the default is yes.
Additional context
On 2.107.0, db push confirms through PromptYesNo in apps/cli-go/internal/utils/console.go, called with the default set to true from apps/cli-go/internal/db/push/push.go. parseYesNo accepts only y/yes/n/no. Any other non-empty string, including u, returns nil, and PromptYesNo then returns the default:
input, err := c.PromptText(ctx, labelWithChoice)
if len(input) > 0 {
if answer := parseYesNo(input); answer != nil {
return *answer, nil
}
}
return def, err
There is no re-prompt and no message that the input was ignored. For db push, def is true, so a typo applies remote migrations.
On current develop (and the 2.118.0 tree), apps/cli-go/internal/db/push/push.go is gone and interactive db push goes through promptYesNo in apps/cli/src/command-internal/prompt-yes-no.ts. A real TTY uses clack confirm, where y and n submit immediately and Enter submits the initial value. That interactive UI does not show the [Y/n] u line from 2.107.0. The shared fallback is still there for a non-TTY read: a non-empty line that parseYesNo does not understand falls through to defaultValue, and db push passes true. The Go PromptYesNo helper is also still used by other confirmations (db reset, migration repair, migration down, seed buckets) with the same fallback.
I am not opening a pull request yet. CONTRIBUTING.md says an external PR has to wait until this issue is open and carries open-for-contribution, and .github/scripts/contribution-gate.ts closes PRs that skip that. Happy to send the fix once that label is on.
- Lenguaje dominante
- TypeScript
- Estrellas
- 2.4k
- Forks
- 526
- Merge medio
- 1 d 2 h
- PR fusionados (30 d)
- 287
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de supabase/cli
-
db diff (migra): session search_path/role applied once per pool, lost on idle reconnect → spurious drop+create and REVOKE floodsPosiblemente ocupada @7ttp la tomó hace 1 día. Abierto🐛 Bug supabase/cli
supabase/cli#6860 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
functions serve: SIGTERM to a stale process kills unrelated processes via kill(-pid) on reused child PIDsPosiblemente ocupada @7ttp la tomó hace 1 día. Abierto🐛 Bug supabase/cli
supabase/cli#6858 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
🐛 Bug supabase/cli
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
-
🐛 Bug supabase/cli
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
-
🐛 Bug supabase/cli
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
supabase/cli#6847 · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de supabase/cli
Issues similares
-
needs:triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
ai-discovered
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
jessepollak/home#1627 ·
Los mantenedores suelen responder en 1 día
-
agent-canvas bug llm priority:low ready-for-dev
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
OpenHands/OpenHands#17806 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
radius-project/ai-extensions#923 ·
Los mantenedores suelen responder en 1 día