15.1.0.34-rc0

chore: create tags and GH releases when we build an AMI

Adding tags makes it easier to diff the changes that have been made
between releases. At the moment, this information only lives in the
contents of the repository (and we haven't really maintained a
changelog).

v13.3.0

Changes

Reference.

Server

• Base image is now Ubuntu 20.04.
• fail2ban filters for both ports 5432 (PostgreSQL) and 6543 (PgBouncer). (ref)
• There is now the option of building PostgREST on the image.
  • Guides can be found here:
    • AWS
    • Digital Ocean

Postgres

• Update to Postgres 13.3. (ref)
• Postgres is now always built from source. (ref)
• ARM64 instances are compiled with Large System Extensions. (ref)
• Install pgRouting extension.
• Install wal2json extension.

Others

Versioning

• Major and minor versions of Supabase Postgres will now follow that of PostgreSQL.
• In the situation wherein there are no updates to PostgreSQL in between releases, the patch version will be bumped up.

Docker

• supabase/postgres 13.3.0.
• Building new docker images would now use the same Ansible task files as when building cloud images. (ref)
• An updated guide on building your own docker image can be found here.

v0.13.0

Changes

Reference.

Server

• Install daemontools.
• Install WAL-G.

Postgres

• Install pgjwt
• Install pgsql-http
• Install plpgsql_check
• Install PL/Java
• Remove readonly role.

Others

Docker

supabase/postgres:0.13.0

v0.12.0

Added

Reference.

Server

• Install Fail2ban.
• Install Unattended Upgrades.
• Removal of common passwords. Users would now need to set up the password for the db superuser postgres before being able to fully use it.

Postgres

• Install pgAudit.

Others

Docker

supabase/postgres:0.12.0

Misc.

• Following semantic versioning from now on. Moved release from patch (v0.0.11) to minor (v0.12.0).