fix(supabase): fix classification of schema changes with COMMENT ON PUBLICATION - #6440
Merged
darkgnotic merged 1 commit intoAug 29, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
darkgnotic
enabled auto-merge
August 29, 2026 01:14
darkgnotic
deleted the
darkgnotic/fix-comment-on-publication-misclassification
branch
August 29, 2026 01:30
darkgnotic
added a commit
that referenced
this pull request
Aug 29, 2026
…UBLICATION (#6440) Fix the classification of schema change type when processing a `COMMENT ON PUBLICATION` tag. Examining the previous schema change is incorrect as in Supabase the `ALTER PUBLICATION` will be missing. So always consider a schema change detected by `COMMENT ON PUBLICATION` as "unknown" which will correctly initiate a backfill for new tables/columns. Context: * https://rocicorp.slack.com/archives/C0B3A4P3W56/p1787956562056209
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.
Fix the classification of schema change type when processing a
COMMENT ON PUBLICATIONtag. Examining the previous schema change is incorrect as in Supabase theALTER PUBLICATIONwill be missing. So always consider a schema change detected byCOMMENT ON PUBLICATIONas "unknown" which will correctly initiate a backfill for new tables/columns.Context: