-
Notifications
You must be signed in to change notification settings - Fork 32
Drop tools.go in favor of native tool directive support in go 1.24 #535
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
Conversation
github: strip away v prefix during bundle submission Signed-off-by: Feruzjon Muyassarov <[email protected]>
@fmuyassarov I'm not against this at all, but could we delay this until we manage to get most of the other functional PR's merged ? We have a bit of a crunch going on ATM, so I'd prefer to focus on getting those merged first. |
Absolutely. You can ping me here whenever you will ready for this change. Thanks. |
@fmuyassarov Then again, if those CI failures would go away by simply bumping golang to 1.24.x in go.mod, then there is no need to delay this. We can do so and merge this once it is updated. |
I pulled this in and it looks like the problems go away by a go get k8s.io/client-go/tools/[email protected] && \
go mod tidy && \
git commit -m -s "go.{mod,sum} update and tidy deps." After that |
Signed-off-by: Feruzjon Muyassarov <[email protected]>
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.
Thanks @fmuyassarov. The PR also updates the deps (especially k8s.io/code-generator). That's fine assuming you've tested that code-generation still works :) Suggestion: that could be mentioned in the commit message.
LGTM from me
Generate target was ran successfully. I assume it is safe to bump the generator library.
|
Yes, there is a verify-generate target/CI job which runs that and checks that there are no changes. That having passed should mean that the generator has verbatim generated the same content as already committed to the repo, so it should be fine. |
No description provided.