fix: remove jwt key validation to allow new api keys #1151
Merged
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
Pull Request Test Coverage Report for Build 15784602486Details
💛 - Coveralls |
# Conflicts: # tests/test_client.py
grdsdev
force-pushed
the
guilherme/clibs-210-supabase-py-does-not-handle-the-new-api-keys-secret-keys
branch
from
07df914 to
064326b
Compare
silentworks
approved these changes
Jun 20, 2025
|
@grdsdev I'm now wondering if we should check if its not the new api key by checking for the |
|
Actually ignore my last comment. Lets remove these check all together. I just checked the JS libraries and we aren't doing such checks since the auth server will handle the validation. |
grdsdev
deleted the
guilherme/clibs-210-supabase-py-does-not-handle-the-new-api-keys-secret-keys
branch
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?
Close #1150
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.