-
Notifications
You must be signed in to change notification settings - Fork 81
build(deps): bump github.com/openshift-online/ocm-cli from 1.0.10 to 1.0.11 #891
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
Open
dependabot
wants to merge
1
commit into
main
Choose a base branch
from
dependabot/go_modules/github.com/openshift-online/ocm-cli-1.0.11
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
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.
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:
cat go.mod | head -50Repository: openshift/backplane-cli
Length of output: 1949
🏁 Script executed:
rg -n "k8s\.io" go.modRepository: openshift/backplane-cli
Length of output: 712
🌐 Web query:
kubernetes k8s.io version compatibility requirements apimachinery api client-go alignment💡 Result:
k8s.io/client-go,k8s.io/apimachinery, andk8s.io/apito the same Kubernetes minor (and ideally same patch) tag. These repos are synced from Kubernetesstaging/and are intended to be consumed as a matched set; mixing minors is a common cause of scheme/serialization/type and generated-client breakage. In particular,client-goexplicitly depends on companion libs (apimachinery,api) and says they must be vendored in “correspondingly matching versions”. [1][2]v1.X.Y↔k8s.io/client-go v0.X.Y(and typicallyk8s.io/api v0.X.Y,k8s.io/apimachinery v0.X.Y).client-gopublishes matching tags and explains thatkubernetes-1.X.Yandv0.X.Ycorrespond to the same staged code. [1]apimachinery(or otherk8s.io/*staging libs).apimachinerystates there are no compatibility guarantees and that branches track Kubernetes. Treat it as “must match Kubernetes/client-go”. [3]client-goprovides a “compatibility matrix” showing “exact match” vs “skew” behavior across Kubernetes versions, and notes older clients often work with newer clusters due to Kubernetes’ backward compatibility—but that’s separate from the requirement to keep the Go modules (api/apimachinery/client-go) aligned with each other. [1]Practical requirement: pick one Kubernetes minor
Xand keep allk8s.io/{client-go,api,apimachinery}atv0.X.*(sameX; preferably same patch*) to avoid mismatched generated types/schemes/negotiation code. [1][3]Sources:
[1] kubernetes/client-go README (versioning + compatibility matrix + matching tags) (github.com)
[2] “Introducing client-go version 6” (client-go requires matching
api/apimachineryversions) (kubernetes.io)[3] pkg.go.dev
k8s.io/apimachinery(explicitly: no compatibility guarantees; tracks Kubernetes) (pkg.go.dev)Citations:
Kubernetes package version mismatch: align
k8s.io/apimachinerywith otherk8s.iopackages.k8s.io/apimachineryv0.34.3 is misaligned withk8s.io/apiv0.30.3,k8s.io/cli-runtimev0.30.3, andk8s.io/client-gov0.30.3. These packages are synced from Kubernetes staging/ and must be consumed as a matched set at the same minor version. Kubernetes explicitly documents that mixing minors is a common cause of scheme, serialization, and type conflicts. Updatek8s.io/apimachineryto v0.30.3 to match the others.🤖 Prompt for AI Agents