-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrade json-patch to v4.11.0 #102467
upgrade json-patch to v4.11.0 #102467
Conversation
Skipping CI for Draft Pull Request. |
Looks like json-patch also released v4.10.0 to make the fix available in the v4 stream. That seems like it might be a better version to switch to. |
/hold |
Thanks @pacoxu for looking into this. |
v4.11.0 should be out and fixed per evanphx/json-patch#145 (comment) |
Signed-off-by: pacoxu <[email protected]>
Thanks. @BenTheElder |
/hold cancel |
dependency update looks great. would be good to add an explicit test case to cover #98080 to ensure this works as expected with this update and does not regress in the future |
Signed-off-by: pacoxu <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, liggitt, pacoxu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #98080
refer to https://github.com/evanphx/json-patch/releases/tag/v5.5.0 which include the fix evanphx/json-patch#143
Special notes for your reviewer:
We upgrade to 4.11.0 for nulls in arrays merge.
And we don't choose v5.5.0 for its Break change:
Does this PR introduce a user-facing change?