0.21.0 - The one with better Supabase support

[justinvdm]

If you are using Snaplet to restore to a development database on Supabase, you may have run into issues where Snaplet attempts to drop or restore data for schemas created by Supabase, for example:

✖ Database: Could not drop schemas to "reset database"
error: schema "pgsodium_masks" does not exist

You may have also run into role-related issues when restoring to a development database on Supabase, for example:

A schema can only be dropped by its owner or a superuser.

If you did not run into either, chances are you would’ve run into the latter issue from November 5 2022 onwards, as Supabase are rolling out a security patch that will prevent superuser access (you would’ve seen this issue already if you’ve already opted into that security patch).

This release aims to solve these issues: if your database is on Supabase, we exclude the following schemas when capturing from your production database, and when restoring to your development database:

graphql, graphql_public, auth, storage, realtime, pgsodium_masks, pgsodium, pgbouncer