Arch Linux User Repository

I have updated the package to include supabase-go while it is still necessary.

Also applied @vitaliikuzhdin's suggestion regarding the license (thanks).

Personally I no longer use supabase so I'd like to stop maintaining this, however given the current situation of the AUR I will not orphan it (I don't want someone to turn it into malware). If someone wants it feel free to email me. If you have an old enough AUR account and a track record of maintaining other packages I can add you as co-maintainer and eventually give you the package.

I have been using this script to automate the fix when updating:

#!/usr/bin/env bash
set -euo pipefail

# Fetch latest PKGBUILD from AUR
curl -sL "https://aur.archlinux.org/cgit/aur.git/plain/PKGBUILD?h=supabase-bin" -o PKGBUILD

# Add supabase-go binary install if missing
if ! grep -q 'install -vDm755 supabase-go' PKGBUILD; then
  sed -i '/install -vDm755 supabase "\$pkgdir\/usr\/bin\/supabase"/a\  install -vDm755 supabase-go "$pkgdir/usr/bin/supabase-go"' PKGBUILD
fi

# Update checksums (requires updpkgsums from pacman-contrib)
if command -v updpkgsums &>/dev/null; then
  updpkgsums
fi

echo "Done. Run 'makepkg -si' to build and install."

Usage: ./update.sh && makepkg -si

It fetches the latest PKGBUILD from AUR, injects the missing supabase-go install line if it's not already there, and optionally updates checksums. You'll need pacman-contrib for updpkgsums.

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.