Description
When installing supabase via the tap (brew install supabase/tap/supabase), the CLI incorrectly shows a spurious update warning on every command because the update checker reads an empty version string.
Steps to Reproduce
brew tap supabase/tap
brew install supabase/tap/supabase
supabase stop # or any supabase command
Actual Behavior
A new version of Supabase CLI is available: v2.100.1 (currently installed v)
We recommend updating regularly for new features and bug fixes: ...
Note: currently installed v has no version number after v.
Expected Behavior
No update warning should appear, since the installed version already is v2.100.1.
supabase --version correctly returns 2.100.1, confirming the binary itself is the right version.
Root Cause
The Supabase CLI (Go) uses two separate version variables:
- One consumed by the
--version flag — correctly set to 2.100.1
- One consumed by the update checker — left as empty string
""
Both should be populated via -ldflags at build time, e.g.:
-X github.com/supabase/cli/internal/utils.Version=2.100.1
The tap formula appears to be injecting the version for the --version path but missing the ldflags injection for the variable the update checker reads. When the update checker sees "", it treats any released version as newer and prints the warning.
Environment
- macOS (Apple Silicon)
- Homebrew tap install:
supabase/tap/supabase 2.100.1
supabase --version → 2.100.1which supabase → /opt/homebrew/bin/supabase → symlink to Cellar/supabase/2.100.1/bin/supabase
Impact
Cosmetic/low severity — the CLI works correctly. However the persistent warning is misleading and may cause users to repeatedly attempt unnecessary upgrades.
Description
When installing
supabasevia the tap (brew install supabase/tap/supabase), the CLI incorrectly shows a spurious update warning on every command because the update checker reads an empty version string.Steps to Reproduce
brew tap supabase/tap brew install supabase/tap/supabase supabase stop # or any supabase commandActual Behavior
Note:
currently installed vhas no version number afterv.Expected Behavior
No update warning should appear, since the installed version already is v2.100.1.
supabase --versioncorrectly returns2.100.1, confirming the binary itself is the right version.Root Cause
The Supabase CLI (Go) uses two separate version variables:
--versionflag — correctly set to2.100.1""Both should be populated via
-ldflagsat build time, e.g.:The tap formula appears to be injecting the version for the
--versionpath but missing the ldflags injection for the variable the update checker reads. When the update checker sees"", it treats any released version as newer and prints the warning.Environment
supabase/tap/supabase 2.100.1supabase --version→2.100.1which supabase→/opt/homebrew/bin/supabase→ symlink toCellar/supabase/2.100.1/bin/supabaseImpact
Cosmetic/low severity — the CLI works correctly. However the persistent warning is misleading and may cause users to repeatedly attempt unnecessary upgrades.