Update PyJWT to 2.9 #299
Merged
Update PyJWT to 2.9 #299
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
logan-stytch
approved these changes
Nov 11, 2025
Contributor
|
Update version.py for the auto release, btw |
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.
Description
This PR updates PyJWT to 2.9 to resolve a bug in local JWT validation.
Local JWT validation was silently failing, forcing unnecessary fallbacks to the Stytch API.
Root Cause: The SDK passes
allowed_issuers: List[str]to PyJWT'sdecode()function, but PyJWT versions 2.4.x-2.8.x only acceptedstr | Nonefor the issuer parameter. This caused a type mismatch where string vs list comparison always returned False, incorrectly rejecting all valid JWTs with "Invalid issuer" errors.Support for lists in issuers was added to PyJWT in 2.9.0: https://pyjwt.readthedocs.io/en/stable/changelog.html?utm_source=chatgpt.com#v2-9-0