User requests that go.mod go and toolchain remain at patch 0. ie. go 1.22.0 because they do not have available in their downstream system a new enough go to compile and build 1.22.8.
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
:+1: for "The project would be better with this feature added"
:-1: for "This feature will not enhance the project in a meaningful way"
blackpiglet
commented
1 day ago
Describe the problem/challenge you have
User requests that go.mod go and toolchain remain at patch 0. ie.
go 1.22.0because they do not have available in their downstream system a new enough go to compile and build1.22.8.The Go toolchain refuses to load a module or workspace that declares a minimum required Go version greater than the toolchain’s own version.
Describe the solution you'd like
The ask is that golang pinning like in https://github.com/vmware-tanzu/velero/commit/7cd92a5aac33c54b3e979775bd45e142615f8320 should be limited to outside of
go.modfiles.We will still be able to fix CVEs by bumping toolchains used to newer go even with go.mod
go 1.22.0Anything else you would like to add:
Being fixed in https://github.com/vmware-tanzu/velero/pull/8399
Slack: https://kubernetes.slack.com/archives/C6VCGP4MT/p1731439622318149?thread_ts=1730991728.424729&cid=C6VCGP4MT
Environment:
velero version):kubectl version):/etc/os-release):Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.