Repository navigation
Conversation
Expose the existing parameter in the API reference.
Document the default and distinguish header ordering from payload ordering.
Add the required unreleased changelog entry.
This branch has not been deployed
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.
jwt.encodealready acceptssort_headers, but the API reference leaves it out of both the signature and parameter descriptions.This documents the default, how to disable sorting, and that it only affects the JOSE header, not the payload. Runtime behavior is unchanged.
Checked on Python 3.14: 472 tests passed, 4 skipped, the Sphinx build passed with warnings treated as errors, and Ruff passed for the changed module. Also checked both header orders, unchanged payload order, and signature verification for both settings.