Description
Sorry I dont really know this stuff, but i can assure you that i have tried several machines, WLE and github codespaces just to try to deploy my simple project, but all show the same problem more or less. And gemini-2.5-flash-preview-04-17 is really confused with it all ;)
Describe the bug
Steps to reproduce: Beskriv exakt vad du gjorde:
Started a GitHub Codespace (specify image if possible, often default Ubuntu).
Installed Homebrew (/bin/bash -c "$(curl -fsSL ...))
Ran Homebrew's "Next steps" to add to PATH (eval ...).
Ran brew install supabase/tap/supabase.
Observed brew install reported success (🍺 ... 2.22.6: ... built in ...).
Ran supabase version -> Error: unknown command "version"....
Ran supabase --debug -> Output showed version 2.22.6 and listed version and hosting.
Ran supabase hosting deploy -> Error: unknown command "hosting"....
Expected behavior: supabase version should show the version number. supabase hosting deploy should proceed with the deployment process.
Actual behavior: Both version and hosting deploy commands report "unknown command" despite being listed in --debug output.
Environment details:
OS: GitHub Codespaces (Linux, specify kernel if known from terminal like uname -a)
Supabase CLI version: 2.22.6 (installed via Homebrew)
Homebrew version: 4.4.32 (from your log)
Shell: Bash (from your prompt)
Terminal: VS Code integrated terminal (in Codespaces)
Relevant Logs/Screenshots: Klistra in de loggar du har visat mig som tydligt visar felet för version och hosting deploy, och outputen från supabase --debug. Detta är väldigt viktigt för dem att förstå problemet.
Vad kan det bero på? (Förslag att nämna i bugg-rapporten om du vill):
Du kan nämna att beteendet är extremt ovanligt och verkar indikera ett problem med hur CLI binären parsas eller exekveras i just den miljön, trots att den startar och visar hjälptexten. Att det händer med både version (en inbyggd flagga/kommando) och hosting (ett subkommando) är förbryllande.
console
unknown command "version" for "supabase"
Try rerunning the command with --debug to troubleshoot the error.
@FredrikKindahl ➜ /workspaces/bingin-simple (main) $ supabase --debug
Supabase CLI 2.22.6
Usage:
supabase [command]
Quick Start:
bootstrap Bootstrap a Supabase project from a starter template
Local Development:
db Manage Postgres databases
gen Run code generation tools
init Initialize a local project
inspect Tools to inspect your Supabase project
link Link to a Supabase project
login Authenticate using an access token
logout Log out and delete access tokens locally
migration Manage database migration scripts
seed Seed a Supabase project from supabase/config.toml
services Show versions of all Supabase services
start Start containers for Supabase local development
status Show status of local Supabase containers
stop Stop all local Supabase containers
test Run tests on local Supabase containers
unlink Unlink a Supabase project
Management APIs:
branches Manage Supabase preview branches
config Manage Supabase project configurations
domains Manage custom domain names for Supabase projects
encryption Manage encryption keys of Supabase projects
functions Manage Supabase Edge functions
network-bans Manage network bans
network-restrictions Manage network restrictions
orgs Manage Supabase organizations
postgres-config Manage Postgres database config
projects Manage Supabase projects
secrets Manage Supabase secrets
snippets Manage Supabase SQL snippets
ssl-enforcement Manage SSL enforcement configuration
sso Manage Single Sign-On (SSO) authentication for projects
storage Manage Supabase Storage objects
vanity-subdomains Manage vanity subdomains for Supabase projects
Additional Commands:
completion Generate the autocompletion script for the specified shell
help Help about any command
Flags:
--create-ticket create a support ticket for any CLI error
--debug output debug logs to stderr
--dns-resolver [ native | https ] lookup domain names using the specified resolver (default native)
--experimental enable experimental features
-h, --help help for supabase
--network-id string use the specified docker network instead of a generated one
-o, --output [ env | pretty | json | toml | yaml ] output format of status variables (default pretty)
-v, --version version for supabase
--workdir string path to a Supabase project directory
Use "supabase [command] --help" for more information about a command.
@FredrikKindahl ➜ /workspaces/bingin-simple (main) $