Questify

2.3.1

Released

Fixes

  • Production Supabase project had an empty public schema — every quests/feedback query failed with PostgREST PGRST205 ("Could not find the table ... in the schema cache"). All 24 migrations and seed.sql were applied to production, and the missing profiles row for the pre-trigger signup was backfilled.

Technical changes· 2 entries for database, tooling, CI, tests and docs

CI/CD

  • supabase.yml gains a db-push job that runs supabase db push --include-seed on pushes to main that touch supabase/** (or the workflow file), so migrations and seed data deploy automatically (requires SUPABASE_ACCESS_TOKEN, SUPABASE_PROJECT_REF, and SUPABASE_DB_PASSWORD secrets).

  • The validate job now fails if any seed.sql INSERT lacks an ON CONFLICT / NOT EXISTS guard, keeping the seed safe to replay on every deploy.