Release 2.11.0 - #7
Merged
Merged
Conversation
RFC 8785 integer domain alignment in canonicalize_jcs and the unsafe-integer write policy at signing and new-write boundaries (#6). Canonical JCS bytes move for integers whose decimal spelling differs from the binary64 serialization of the same value, which is why the minor version moves. Signed-off-by: Tymofii Pidlisnyi <tima@aeoess.com>
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.
Release 2.11.0.
What ships
canonicalize_jcsserializesintthrough the RFC 8785 number domain (RFC 8785 integer domain fix and unsafe-integer write policy #6)Compatibility, read this before upgrading
Canonical JCS bytes move for integers whose decimal spelling differs from the binary64 serialization of the same value.
9007199254740992and9007199254740994are unchanged.9007199254740993now emits9007199254740992, 2^60 emits1152921504606847000, and 2^68 emits295147905179352830000.A signature made by 2.10.0 or earlier over an affected value does not verify against bytes recomputed by 2.11.0. Such an artifact already failed for any peer recomputing through the RFC 8785 number domain, including the TypeScript and Go SDKs, so this release moves the failure to one place instead of leaving it to the peer.
Not code
Only
CHANGELOG.md,README.mdandpyproject.tomlmove in this PR. The code landed in #6.Gate on this branch
845 tests pass.
python -m buildproduces the 2.11.0 wheel and sdist.After merge
Tag
v2.11.0on the merge commit.publish.ymlpublishes to PyPI over Trusted Publishing with PEP 740 attestations.