fix(cli): escape backslashes in inspect schema patterns#5568
Merged
Conversation
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase@5568Preview package for commit |
avallete
approved these changes
Jun 13, 2026
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
2 participants
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.
Summary
Escapes backslashes when building SQL LIKE patterns for legacy
inspect dbinternal schema filters.Context
Code scanning flagged the previous sanitizer because it escaped underscores without escaping existing backslashes, which could let a backslash alter the meaning of the following pattern character.
Impact
Backslash-containing schema names now produce literal LIKE patterns while existing internal schema wildcard behavior stays unchanged.