https://stackoverflow.com/questions/67551593/supabase-client-permission-denied-for-schema-public Can we get a better workaround for this?

The migration tool sounds like the issue here, there is no way for Supabase to setup the permissions for you if the migration tool destroys the entire database. It is recommended you only change Schemas that belong to you. Don't modify or delete schemas created by Supabase like

auth, storage, extensions, realtime, pgbouncer, pg_catalog

.

Got it! It was a good learning...Thanks. So basically I should never force migrate. Instead should use

db push

for the my schema updates.