v2.4.1 is an invalid version so the proxy.golang.org couldn't use it.

$ GOPROXY=direct go get github.com/mikefarah/yq@v2.4.1
go: finding github.com/mikefarah/yq v2.4.1
go get github.com/mikefarah/yq@v2.4.1: github.com/mikefarah/yq@v2.4.1: invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v2

This version validation rule is new in go1.13 (https://golang.org/doc/go1.13#modules Version validation).

Will see the same result without proxy.golang.org. (i.e., GOPROXY=direct)
FYI: with go1.14, those v2.x.x+incompatible will be dropped from the list output, and v1.15.0 be the latest one. (See "+incompatible versions" of https://tip.golang.org/doc/go1.14#go-command )

Closing this since it's working as intended.

Sorry - I read that documentation and I don't understand it.

How am I supposed to fix this? I thought we were supposed to use go.mod - but the doco seems to suggest not to use it?

Very confused..

The error message indicates its go.mod file declares the module name module github.com/mikefarah/yq. According to the semantic import versioning convention (https://research.swtch.com/vgo-import), it should be github.com/mikefarah/yq/v2 to be recognized as v2. https://blog.golang.org/v2-go-modules describes how to publish vN (N > 1).

But I am not sure, though, if that's sufficient to completely fix the issue you mentioned.

Have you tried to visit the Gophers' # modules slack channel? I heard a lot of experienced, kind, helpful gophers gather there.

@tbpg @jadekler @bcmills @jayconrod

Updating the module to github.com/mikefarah/yq/v2 worked!

Thanks @hyangah