goanywhere chops off patch version digits from go version, breaking on go 1.24

[quite]

goanywhere for some reason chops off the patch version digits from the go version that is written into the go.work file.

See https://github.com/u-root/gobusybox/blob/main/src/cmd/goanywhere/main.go#L128

*versionFlag = fmt.Sprintf("%d.%d", vers.Segments()[0], vers.Segments()[1])

I'm using go 1.24.4 and get this:

14:07:09 ERROR mkuimage error: failed to resolve package paths: err: exit status 1: stderr: go: module /home/quite/foo/src listed in go.work file requires go >= 1.24.0, but go.work lists go 1.24; to update it:
        go work use

Worked around by passing -v 1.24.0 to goanywhere.

[orangecms]

I would think that the assumption is that patch releases should not break APIs by semver convention - so take the minor part only in order to be able to use any earlier patch release up to the latest.

What you are seeing here looks like a change in conventions though.
Would need some digging to see if Go "broke" this intentionally.

I think your workaround also makes sense to be implemented in goanywhere, and it would be trivial. You already found the line, after all.

However, I see no reason to essentially turn the patch version to 0 instead of just fully preserving it. Anything requiring Go 1.x.0 should be able to use Go 1.x.n for any n. Otherwise Go would break by semver convention.

Or am I missing something? @hugelgupf