-
Notifications
You must be signed in to change notification settings - Fork 73
Master submodule update 06 09 #4186
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
base: master
Are you sure you want to change the base?
Changes from all commits
ddaaf48
39efec5
4fe37b1
bb3543d
b93f10e
32616f8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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/windows-machine-config-operator
Length of output: 43504
Check swag/jsonname behavior change compatibility for the indirect go-openapi bumps.
The
jsonpointer/jsonreferenceupdates are indirect, and current usage shows up only via vendoredk8s.io/kube-openapi. Theswag/jsonnamejump is the main risk:swag v0.26.0introduces a new json name provider, andv0.26.1adds a loading sandbox with security implications. Run the usual verification (e.g.,make verify) to catch any OpenAPI/schema naming regressions.🤖 Prompt for AI Agents
Source: Coding guidelines