0.5.5 — nightly database backups that ride the deploy robot

scheduled-backups.yaml is now a real nightly backup instead of a switched-off draft: every night at 03:27 UTC it dumps the production database (roles, schema, data) with the Supabase CLI and uploads the three files to a date-stamped folder in a Google Cloud Storage bucket you own — daily/ always, weekly/ on Sundays, monthly/ on the 1st, each tier pruned by a lifecycle rule on the bucket. Supabase's free tier keeps no backups; this is yours.

It needs no new secret. The dump reads the migrations workflow's DATABASE_CONNECTION_STRING and the upload runs as the deploy workflow's github-deployer account (GCLOUD_SERVICE_KEY — its storage.admin role covers the bucket), so set up automatic deploys first. Until both secrets exist it skips itself quietly, green. The one-time setup — a bucket, its retention rule, and two values in the env: block — is in the workflow's header; Mosayic's "Back up your database" card does it in one click. On Supabase Pro (daily backups included) disable it from the Actions tab. (Package version stays 0.0.1 by design.)