Merge release 4.0.3 into 4.1.x #711
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
We received reports of users experiencing exceptions when parsing JWTs with timestamps with precision beyond microseconds on time-fractions. This guards against having any kind of edge-case when dealing with floats as input to the creation of DateTimeImmutable objects.
…on-issues Prevent type conversions issues when parsing time-fractions
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.
Release Notes for 4.0.3
This release removes the possibility of having parsing issues when dealing with time-fractions with more than 6 decimal places.
4.0.3
Bug
json_encode()to convert time fractions to microseconds cause precision issues thanks to @sachchida1993