chore: upgrade @supabase/lite to 0.10.0 - #284
Draft
mattrossman wants to merge 2 commits into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
Author
|
Kicking of a regression suite refresh to sanity check: |
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.
Upgrades
@supabase/litefrom0.7.1-next.3to0.10.0(see change notes relevant to evals).When we spin up a fake project we run lite's storage schema, then patch in the bits a real Supabase project has that lite was missing. Lite now ships most of them itself (the
storage.objects.iddefault,storage.foldername(), RLS on both tables), so that patch drops to just the role grants.Refreshing the regression suite on this branch to check the upgrade against every scenario rather than just the storage ones. Will link the snapshot once it lands (reverted to keep results out of this PR). No benchmark refresh, leaving that to AI-1204.
The RPC assertion fix is unrelated to the bump. It was already failing on
mainand simple enough to tie in here.Closes AI-1172