Why specify the exact go version (`1.21.0`) about go-snaps HOT 3 CLOSED

Hey 👋 , thanks for opening this issue. I don't recall any specific reason for using 1.21.0 patch. I didn't know for this interaction so this was probably an oversight on my side when I hanged the version to 1.21.0 instead of 1.21.

I will have a look if there is a reason I did that 😅 . I will also check if I can simlpiy put 1.21 and release a new version of go-snaps, that will fix it and not affect others.

from go-snaps.

Hey, thank you for the quick reply.

It's not a big issue, It's just a bit annoying if the exact version is forced. For us, this caused some minor issues with our CI build.

For reference:

https://go.dev/ref/mod

At go 1.21 or higher:
- The go line declares a required minimum version of Go to use with this module.
- The go line must be greater than or equal to the go line of all dependencies.
- The go command no longer attempts to maintain compatibility with the previous older version of Go.
- The go command is more careful about keeping checksums of go.mod files in the go.sum file.

from go-snaps.

💡 haaa this is what I missed. Thanks for posting this. So if I understand correct just putting 1.21 shouldn't affect anything just allow people to use whatever patch they want. Is that correct?

from go-snaps.