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
Avoid requiring the latest Go toolchain patch version to build #28686
Conversation
Wild assertion from my side but from the upstream issue it looks like Cilium is the unusual one here in forcing the minimum toolchain version to follow the latest patch release. If we're updating this by patch releases for a specific reason, then please bring those issues up. Otherwise I think we can just manually bump this version when Cilium starts using stdlib features that require a new minor release of Go, rather than tracking patch releases. As I understand this should only impact developers, as the actual toolchain used to build Cilium is updated through the dockerfiles. As such, any builds from the CI or for release should be up-to-date for the latest Go patch version. |
Oh, and if there's some other syntax for Renovate to convince it to only bump for minor versions then I'm open to that as well. It's probably worthwhile to ensure that developer toolchains match the minor version of the toolchain being used to build production images. |
6071a34
to
a5db17a
Compare
a5db17a
to
fc1f3ad
Compare
/test |
Nothing in the tree depends on newer patch releases of Go, so we can keep this to the first patch release of this series. Signed-off-by: Joe Stringer <joe@cilium.io>
The goal here is to allow developer toolchains to have more flexibility around the specific version of Go compared with the latest patch releases. Note that all of the real-world code and all tests will continue to be updated to use the latest Go versions, it's just the go.mod that will start to drift, since the code can actually compile with earlier versions of Go; we don't require specific patch versions based on the set of standard library features used in the code. Co-authored-by: André Martins <andre@cilium.io> Signed-off-by: Joe Stringer <joe@cilium.io>
fc1f3ad
to
91d7a49
Compare
/test |
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
Shamelessly copied from cilium/cilium#28686. Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
Shamelessly copied from cilium/cilium#28686. Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
Shamelessly copied from cilium/cilium#28686. Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
Shamelessly copied from cilium/cilium#28686. Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
Forcing developers to change their local toolchain within patch releases
introduces more problems than it's worth. Remove the automatic go.mod
update and don't require newer patch releases of the latest Go version.
Related: #27820
Related: golang/go#63522