refactor(!): Supabase is now an S3-compatible servcices#5663
Merged
Conversation
Signed-off-by: Xuanwo <[email protected]>
github-actions
bot
added
the
releases-note/refactor
Signed-off-by: Xuanwo <[email protected]>
Xuanwo
requested review from
Zheaoli,
messense,
oowl and
suyanhanx
as code owners
messense
approved these changes
Feb 26, 2025
Member
Author
|
Thank you @messense for the review. |
Member
|
We should need an upgrade note for this somehow breaking/notable change. |
Member
Author
Yes! |
Xuanwo
changed the title
Xuanwo
changed the title
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
3 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.
Which issue does this PR close?
Supabase is now an S3-compatible service: https://github.com/supabase/storage
This change also allows us to eliminate some workarounds for failed tests in Supabase.
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?