Deploying a Supabase application

Setup

Item	Kind	Required	When	Done when	How
Supabase CLI 2.120+	user	required	All	`supabase --version` prints 2.120.0 or later	https://supabase.com/docs/guides/local-development/cli/getting-started
Deno	user	optional	Deploy, when the app has Edge Functions	`deno --version` succeeds	https://docs.deno.com/runtime/getting_started/installation/
GitHub CLI	user	required	Deploy, Secrets, Run	`gh auth status` succeeds and `gh repo view` finds the repository	https://cli.github.com, then `gh auth login`; create the GitHub repository and push the project
Supabase login	user	required	Deploy, Provision, Run, Troubleshoot	`supabase projects list` succeeds	`supabase login`
Production project	ask	required	Deploy, Provision	`config.toml` has `[remotes.production]` with a `project_id`	Ask: an existing project from `supabase projects list`, or a new one. Recorded as `[remotes.production] project_id` per configuring-remote-project.md
CI access token	user	required	Secrets	configuring-github-actions.md → Probe reports every permission granted	Per configuring-github-actions.md → CI access token

Setup — for each Setup row whose When covers the request, in order: Done when holds → skip; user → stop and print its How when required, continue without it when optional; ask → fill what the request answers, ask the rest together in one message, record each answer; auto and static → run.
Contract — read deployment-contract.md.
Recipe — match one Recipes row; open every doc in its Read column.