fix: ensure replication connection publication only has correct tables #1657
+191
−21
Conversation
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
filipecabaco
force-pushed
the
fix/recreate-publication-if-incorrect
branch
from
cc7aee3 to
c28394f
Compare
edgurgel
reviewed
Dec 10, 2025
edgurgel
approved these changes
Dec 11, 2025
Member
edgurgel
left a comment
edgurgel
left a comment
There was a problem hiding this comment.
Added a comment about a test but other than that LGTM! Nice one
filipecabaco
force-pushed
the
fix/recreate-publication-if-incorrect
branch
from
5144af3 to
b10132d
Compare
This comment has been minimized.
This comment has been minimized.
Member
|
🎉 This PR is included in version 2.68.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 kind of change does this PR introduce?
Ensures replication connection publication only has correct tables by checking during the connect steps what tables are associated with
supabase_realtime_messages_publication