since the last update, commands like "supabase stop" output errors. I had Claude Code analyse the issue and it's very sure that the error and fix are as follows:

The 2.101.0 release tarball contains two binaries, supabase and supabase-go, but package() only installs supabase. The supabase shim forwards to supabase-go, so commands fail with "Could not find the supabase-go binary". Adding install -vDm755 supabase-go "$pkgdir/usr/bin/supabase-go" to package() fixes it.

Here's the full error that I get:

❯ supabase stop
Could not find the `supabase-go` binary.

The Supabase CLI ships as two co-located binaries: `supabase` (this shim)
and `supabase-go` (the Go CLI that the shim forwards to). The shim looked
for `supabase-go` in:

  • $SUPABASE_GO_BINARY (unset)
  • /usr/bin/supabase-go (not found alongside the shim)
  • @supabase/cli-linux-x64 (npm package not installed)
  • @supabase/cli-linux-x64-musl (npm package not installed)

To fix, do one of:
  • Extract the release tarball into a directory and add the directory to
    PATH (do not move `supabase` somewhere `supabase-go` doesn't follow).
    For example, on this host:

      mkdir -p "$HOME/.local/share/supabase"
      curl -sL https://github.com/supabase/cli/releases/download/v2.101.0/supabase_2.101.0_linux_amd64.tar.gz \
        | tar -xzf - -C "$HOME/.local/share/supabase"
      export PATH="$HOME/.local/share/supabase:$PATH"

  • Install via npm: `npm i -g supabase`.
  • Set SUPABASE_GO_BINARY to the absolute path of `supabase-go`.

@catwell, you should be renaming sources instead, for example:

source=("supabase-${pkgver}-LICENSE::https://raw.githubusercontent.com/supabase/cli/refs/tags/v$pkgver/apps/cli-go/LICENSE")

@locuaz when yay asks you "Packages to cleanBuild?" pick [A]ll. This happens because a previous release of the package was broken and you still have the wrong license file.

I'm getting these errors:

yay -Syu --aur
:: Searching AUR for updates...
 -> Packages not in AUR: accounts-qml-module
 -> Flagged Out Of Date AUR Packages: antigravity
 -> maliit-keyboard: local (2.3.1-4) is newer than AUR (2.3.1-3)
:: 1 package to upgrade/install.
1  aur/supabase-bin  2.98.2-1 -> 2.100.1-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
 -> Excluding packages may cause partial upgrades and break systems
==> 
AUR Explicit (1): supabase-bin-2.100.1-1
:: (1/1) Downloaded PKGBUILD: supabase-bin
  1 supabase-bin                     (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
  1 supabase-bin                     (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
==> Making package: supabase-bin 2.100.1-1 (Tue 19 May 2026 02:40:49 PM -05)
==> Retrieving sources...
  -> Found LICENSE
  -> Downloading supabase_2.100.1_linux_amd64.tar.gz...
  % Total    % Received % Xferd  Average Speed  Time    Time    Time   Current
                                 Dload  Upload  Total   Spent   Left   Speed
  0      0   0      0   0      0      0      0                              0
100 66.39M 100 66.39M   0      0 43.75M      0   00:01   00:01         63.45M
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha256sums...
    LICENSE ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> error downloading sources: /home/user/.cache/yay/supabase-bin 
    context: exit status 1 


:: (1/1) Parsing SRCINFO: supabase-bin
==> Making package: supabase-bin 2.100.1-1 (Tue 19 May 2026 02:40:51 PM -05)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found LICENSE
  -> Found supabase_2.100.1_linux_amd64.tar.gz
==> Validating source files with sha256sums...
    LICENSE ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> error making: supabase-bin-exit status 1
 -> Failed to install the following packages. Manual intervention is required:
supabase-bin - exit status 1

@vitaliikuzhdin I did not remove it, it is still in the repo! But it is a hidden file and I usually don't use nvchecker so I forgot about it. I'll try to automate some way to notify me using it, thanks.

@catwell, back when I maintained this, I used an nvchecker config that did not include pre-releases. You removed it with your first commit to this repo, but it should still work if you restore it. It's still not perfect because GitHub only sends notifications about pre-releases and not releases (or was it an issue on my side?..), but at least it makes the update process semi-automatic.

Thanks @Gurnk, updated.

Due to how Supabase deals with their releases it is difficult to be informed when a new stable release is out (I opened issues on their repo and Repology - see https://github.com/supabase/cli/issues/4067 - but I don't think it will ever be fixed...)

@Gurnk, I am no longer a maintainer.

Hi @vitaliikuzhdin !

Supabase CLI 2.47.2 was released on September 28, 2025. Here's the simple diff for the update:

diff --git a/PKGBUILD b/PKGBUILD
index b2a645f..e904a1d 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,7 +3,7 @@
 # Contributor: Angelo Verlain  <hey@vixalien.com>

 pkgname=supabase-bin
-pkgver=2.39.2
+pkgver=2.47.2
 pkgrel=1
 pkgdesc="CLI for Supabase, an open source Firebase alternative"
 arch=(aarch64 x86_64)
@@ -16,8 +16,8 @@ conflicts=(supabase)
 source_aarch64=("supabase-$pkgver-aarch64.tar.gz::$_url/releases/download/v$pkgver/supabase_linux_arm64.tar.gz")
 source_x86_64=("supabase-$pkgver-x86_64.tar.gz::$_url/releases/download/v$pkgver/supabase_linux_amd64.tar.gz")

-sha256sums_aarch64=("c2156a6efce56a9383bd99f8b69c95548d4477a80ac41d7d74994fea4d43edf0")
-sha256sums_x86_64=("bd13b5afa5bdb06a254b8b24f63bc3ef679e1fb1bb245ee6e842d40955a7b2a5")
+sha256sums_aarch64=('c9f842ee61ba0ed8a8df8d1c99b70e12a0d916ffde4c9b0a8d6e3f8081198167')
+sha256sums_x86_64=('ec0add25c45f2aa85343e832553f661712e874ecd3ed63b7ea2b452a2fa49d71')

 prepare() {
   cd "$srcdir"

@vitaliikuzhdin Thanks kindly for maintaining this. It looks like they've released 2.20.3 now, after a series of pre-releases.

Here's a diff, if helpful. I confirm it builds and is working for me locally.

❯ git diff HEAD~1
diff --git a/PKGBUILD b/PKGBUILD
index 3295993..1bf5b95 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,7 +3,7 @@

 _pkgname="supabase"
 pkgname="${_pkgname}-bin"
-pkgver=2.19.7
+pkgver=2.20.3
 pkgrel=1
 pkgdesc="CLI for Supabase, an open source Firebase alternative"
 arch=('aarch64' 'x86_64')
@@ -15,8 +15,8 @@ conflicts=("${_pkgname}")
 _pkgsrc="${_pkgname}-${pkgver}"
 source_aarch64=("${_pkgsrc}-aarch64.tar.gz::${_url}/releases/download/v${pkgver}/${_pkgname}_linux_arm64.tar.gz")
 source_x86_64=("${_pkgsrc}-x86_64.tar.gz::${_url}/releases/download/v${pkgver}/${_pkgname}_linux_amd64.tar.gz")
-sha256sums_aarch64=('d5f346e5dabb4c40322a1859a430361dfc4c1585fd8ea3790ed834c81247e330')
-sha256sums_x86_64=('0ba916f9bd03060d7c64b7dda755df14568b66a6c4b619c3029d1aeb75fea43a')
+sha256sums_aarch64=('ac32329fcd249deb8d06e62b6a0d8fb9dc04186986e2cb0766d6593fd73b8d23')
+sha256sums_x86_64=('11a7332c09d56571f9ec2a4871660b5e7b13c34f75c9947d3870e15805e72211')

 prepare() {
   cd "${srcdir}"