-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Fix verify godeps failure on 1.14 #77239
Conversation
/priority critical-urgent |
/lgtm |
Do we need the same for 1.12 and 1.13? |
github.com/evanphx/json-patch added a new tag at the same sha this morning: https://github.com/evanphx/json-patch/releases/tag/v4.2.0 This confused godeps. This PR updates our file to match godeps expectation. Fixes issue 77238
Yes, both use 5858425f75500d40c52783dce87d085a483ce135: |
I'll send those too |
/assign @dougm @aleksandra-malinowska @tpepper |
whoops that was for 1.13 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cblecker, liggitt, mtaufen 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 |
/retest |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
github.com/evanphx/json-patch added a new tag at the same sha this
morning: https://github.com/evanphx/json-patch/releases/tag/v4.2.0
This confused godeps. This PR updates our file to match godeps
expectation.
Which issue(s) this PR fixes:
Fixes: #77238
Does this PR introduce a user-facing change?: