Remove patch version in go.mod's

[johanbrandhorst]

9fdb1ca updated the go stanza in the go.mod files in this repo to 1.23.0. In some cases, it was changed from go 1.22 to go 1.23.0. That might seem insignificant, but it turns out that this can cause all kinds of annoying problems for downstream problems (see discussion on grpc-go/grpc repo) and ideally libraries should (for now at least) not use the patch version at all. Please consider changing to go 1.23 consistently.

[liggitt]

Given go tooling adds the patch version by default, it's really hard (almost impossible) to try to keep it out of individual modules. I'd suggest resolving that in go tooling before trying to chase the whole internet of dependencies to keep patch versions out

xref kubernetes/kubernetes#124385 (comment)

[johanbrandhorst]

It is being discussed: golang/go#65847. If you don't want to make the change, I respect that.

[quartzmo]

@johanbrandhorst Per commentary on golang/go#65847, it seems to me that declaring a 0 value patch version is acceptable for the moment (until the Go team addresses patch versions in the go directive, if ever). Is there any immediate problem for you if we keep our go.mod go versions at 1.2x.0?

[johanbrandhorst]

I think staying at 1.x.0 is likely fine, if that's something you're happy to commit to we can close this issue.

[quartzmo]

if that's something you're happy to commit to we can close this issue

We will try our best to maintain the 0 value patch versions. If one of our dependencies updates to a higher patch version, we'll ask them to restore the 0 patch version, and delay updating the dependency version until they do so. Only if absolutely necessary will we allow a dependency to force us to increase the patch version.