Revert to json-patch 4.12.0 #120327
Merged
Revert to json-patch 4.12.0 #120327
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
k8s-ci-robot
added
release-note
Contributor
k8s-ci-robot
added
approved
skitt
added a commit
to skitt/kubernetes
that referenced
this pull request
May 28, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]>
k8s-publishing-bot
pushed a commit
to kubernetes/apimachinery
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/api
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/client-go
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/code-generator
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/component-base
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/component-helpers
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/apiserver
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/kube-aggregator
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/sample-apiserver
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/sample-controller
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/apiextensions-apiserver
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/metrics
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/cli-runtime
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/sample-cli-plugin
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/kube-proxy
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/cri-client
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/kubelet
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/kube-scheduler
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/controller-manager
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/cloud-provider
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/kube-controller-manager
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/cluster-bootstrap
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/csi-translation-lib
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/kubectl
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/pod-security-admission
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/dynamic-resource-allocation
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
k8s-publishing-bot
pushed a commit
to kubernetes/endpointslice
that referenced
this pull request
May 29, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes/kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]> Kubernetes-commit: 5300466a5c8988b479a151ceb77f49dd00065c83
YamasouA
pushed a commit
to YamasouA/kubernetes
that referenced
this pull request
Jul 24, 2024
The canonical import for json-patch v4 is gopkg.in/evanphx/json-patch.v4 (see https://github.com/evanphx/json-patch/blob/master/README.md#get-it for reference). Using the v4-specific path should also reduce the risk of unwanted v5 upgrade attempts, because they won't be offered as automated upgrades by dependency upgrade management tools, and they won't happen through indirect dependencies (see kubernetes#120327 for context). Signed-off-by: Stephen Kitt <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What type of PR is this?
/kind bug
/kind regression
What this PR does / why we need it:
Fixes #120326
Does this PR introduce a user-facing change?
/assign @Jefftree