-
Notifications
You must be signed in to change notification settings - Fork 100
Bump github.com/evanphx/json-patch from 4.12.0+incompatible to 5.9.11+incompatible #478
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
Merged
openshift-merge-bot
merged 1 commit into
master
from
dependabot/go_modules/github.com/evanphx/json-patch-5.9.11incompatible
Apr 23, 2026
+3
−4
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
🧩 Analysis chain
🏁 Script executed:
Repository: openshift/managed-cluster-validating-webhooks
Length of output: 653
The go.mod entry uses the
+incompatiblesuffix, which indicates improper Go module versioning.Line 6 shows
github.com/evanphx/json-patch v5.9.11+incompatible. The+incompatiblesuffix means this library is using v5 semantics but without adopting the proper/v5import path convention for Go modules v1.11+. The codebase correctly imports it asgithub.com/evanphx/json-patch(unversioned) in one location. The versioned path (github.com/evanphx/json-patch/v5) appearing in go.mod is a transitive dependency—this is normal and not a problem.The concern is whether this library should be migrated to its proper versioned import path if the library maintainers have adopted that convention. Verify the upstream library's current status and consider updating the import if a properly-versioned version is available.
🤖 Prompt for AI Agents
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.
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.
@diakovnec, that's a thorough and well-reasoned analysis — agreed on all points. To confirm: the upstream library itself recommendsgo get -u github.com/evanphx/json-patch/v5as the "latest and greatest" path, and thegithub.com/evanphx/json-patch/v5module is fully available on pkg.go.dev with the complete API. So the migration path is clean when you're ready for it.Your summary is spot on:
#478as-is — the v4→v5 upgrade is the valuable change herepkg/webhooks/service/service_test.gofromgithub.com/evanphx/json-patchtogithub.com/evanphx/json-patch/v5and updatego.modaccordinglyWould you like me to open a follow-up GitHub issue to track the import path cleanup?