2.3.1
Released
Fixes
Production Supabase project had an empty
publicschema — every quests/feedback query failed with PostgRESTPGRST205("Could not find the table ... in the schema cache"). All 24 migrations andseed.sqlwere applied to production, and the missingprofilesrow for the pre-trigger signup was backfilled.
Technical changes· 2 entries for database, tooling, CI, tests and docs
CI/CD
supabase.ymlgains adb-pushjob that runssupabase db push --include-seedon pushes tomainthat touchsupabase/**(or the workflow file), so migrations and seed data deploy automatically (requiresSUPABASE_ACCESS_TOKEN,SUPABASE_PROJECT_REF, andSUPABASE_DB_PASSWORDsecrets).The validate job now fails if any
seed.sqlINSERT lacks anON CONFLICT/NOT EXISTSguard, keeping the seed safe to replay on every deploy.