Allow newer PyJWT versions for branch 5.3#3682
Merged
petyaslavova merged 1 commit intoredis:5.3from Jul 8, 2025
Merged
Conversation
Backported from the master branch (redis#3636). Co-authored-by: Armin Berres <berres@weplan.info>
petyaslavova
approved these changes
Jul 8, 2025
Collaborator
|
Hi @bcmills, thanks for taking the time to prepare this PR! I will merge it today and will prepare a patch release by the end of the week. |
|
Hi @petyaslavova may I ask when we will have this patch release in? |
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
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.
Backported from the master branch (#3636).
Pull Request check-list
Please make sure to review and check all of these items:
NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Description of change
Allow PyJWT versions newer than
2.9.*, since there are not any known compatibility issues with those. This change is already present in the master branch; it just needs to be backported and released on the 5.3 branch.