chore: add Supabase migration deploy workflow#3
Merged
Conversation
Co-authored-by: Ona <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
zacharias-ona
commented
Apr 14, 2026
| -H "Authorization: Bearer ${SUPABASE_KEY}" 2>&1) | ||
| if echo "$body" | grep -qE "PGRST(204|205)"; then | ||
| echo "MISSING COLUMN: ${table}.${column} — $body" | ||
| failed+=("${table}.${column}}") |
Collaborator
Author
There was a problem hiding this comment.
Bug: extra } — this appends values like pages.is_private} to the failed array, corrupting the error summary on line 76.
Suggested change
| failed+=("${table}.${column}}") | |
| failed+=("${table}.${column}") |
This was referenced Apr 16, 2026
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a GitHub Actions workflow that deploys Supabase migrations on push to main and verifies critical tables/columns exist via the PostgREST API.
How
supabase/setup-cli@v1to install the Supabase CLISUPABASE_PROJECT_IDsecretsupabase db pushto apply pending migrationspage_versions,collections,collection_views,collection_rows,comments) and columns (pages.is_private,pages.cover,pages.share_token) exist in the schema cacheworkflow_dispatchfor manual runsRequired secrets
SUPABASE_ACCESS_TOKENSUPABASE_DB_PASSWORDSUPABASE_PROJECT_IDNEXT_PUBLIC_SUPABASE_URLNEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEYTesting
Workflow syntax validated. Will run on first push to main with migrations present.
Checklist
anytypes