Update json-path to version 2.8.0 - introduces a breaking change #196
Conversation
This file contains 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
scholzj
approved these changes
Jun 28, 2023
…ow `oauth.custom.claim.check` queries using `== null` or `!= null` are handled Signed-off-by: Marko Strukelj <[email protected]>
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.
Previous versions of json-path had a bug in evaluation of queries that tested equality against
null.Some queries that used to evaluate to
falsenow evaluate totrueand vice-versa.This was a known issue that is described in README.md together with a description of how to properly avoid using
nullin queries.This version bump is needed to address CVEs.