v1.5.1

Fixed

• Supabase — Fix make update breaking existing databases by silently upgrading Postgres across major versions (e.g. 15.8.1.085 → 17.6.1.136), which left supabase-db unhealthy and aborted the update. The installer now detects the major version of the data already on disk (PG_VERSION) and pins supabase/postgres to a compatible tag after pulling upstream changes. Fresh installs continue to follow upstream (PG17); existing PG15 volumes stay on PG15 until you migrate manually (#64).

Upgrade

make update

During Supabase startup you should see Pinned Supabase Postgres to supabase/postgres:15.8.1.085 …, and supabase-db will stay on your existing major version (running (healthy)). Repeated updates are idempotent — the major version is no longer bumped silently.

Full Changelog: v1.5.0...v1.5.1