db push applies migrations when the confirmation answer is not yes or no
I maintainer di solito rispondono entro 1 giorno
@7ttp ci sta già lavorando.
Dal 28/9/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
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.
- Lingua principale
- TypeScript
- Stelle
- 2.4k
- Fork
- 526
- Merge medio
- 1g 2h
- PR unite (30g)
- 287
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di supabase/cli
-
db diff (migra): session search_path/role applied once per pool, lost on idle reconnect → spurious drop+create and REVOKE floodsForse già presa @7ttp l’ha presa oggi. Aperta🐛 Bug supabase/cli
supabase/cli#6860 · 1 commento · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
functions serve: SIGTERM to a stale process kills unrelated processes via kill(-pid) on reused child PIDsForse già presa @7ttp l’ha presa 1 giorno fa. Aperta🐛 Bug supabase/cli
supabase/cli#6858 · 1 commento · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
🐛 Bug supabase/cli
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
I maintainer di solito rispondono entro 1 giorno
-
🐛 Bug supabase/cli
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
I maintainer di solito rispondono entro 1 giorno
-
🐛 Bug supabase/cli
Difficoltà 3/5 1-2 giorni Idoneità per principianti 68/100
supabase/cli#6847 · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di supabase/cli
Issue simili
-
documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
inu-appcenter/memorIN-frontend#106 ·
I maintainer di solito rispondono entro 1 giorno
-
kind/bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
I maintainer di solito rispondono entro 7 giorni
-
[Bug] @deck.gl/arcgis dist import resolves to unpublished @deck.gl/core source path (9.3.11, 9.4.0)Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
fix: CopyFilters ignores tabApertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
CSCfi/sd-search-ui#145 ·
I maintainer di solito rispondono entro 1 giorno
-
Add: Cbeebies pl SDApertacheck:passed streams:add
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno