-
Notifications
You must be signed in to change notification settings - Fork 41.4k
Update to spf13/pflag to prevent CI break #133823
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
Update to spf13/pflag to prevent CI break #133823
Conversation
I went ahead and cut a https://github.com/spf13/cobra/releases/tag/v1.10.0 @dims not sure if you want to include the new cobra to achieve something like:
|
@jpmcb sounds good! added a commit for cobra as well. |
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.
/lgtm
LGTM label has been added. Git tree hash: 328c0052a61915a8aea6af3878b6daf11cddf658
|
/triage accepted |
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.
/lgtm
Looks like a temporary glitch |
Fix for #133809
There was a breaking change in pflags 1.0.8, which was fixed in 1.0.9:
spf13/pflag@v1.0.8...v1.0.9
We could do nothing and CI will pick up 1.0.9, but i'd prefer us to update to 1.0.9 to prevent any users of our libraries to pick the fixed/updated version (and not let them pick the broken 1.0.8 by mistake)
What type of PR is this?
/kind bug
/kind failing-test
What this PR does / why we need it:
Which issue(s) this PR is related to:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: