Latest tags are not compatible with Go module versioning scheme about ccache HOT 5 CLOSED

Sorry about that, don't do much go anymore so didn't know Updated.

from ccache.

Publishing the tags alone does not solve this. See below,

> go get -v -u github.com/karlseguin/ccache/[email protected]
go: finding github.com v2.0.4
go: finding github.com/karlseguin/ccache v2.0.4
go: finding github.com/karlseguin v2.0.4
go: finding github.com/karlseguin/ccache/v2 v2.0.4
go: finding github.com/karlseguin/ccache/v2 v2.0.4
go: finding github.com/karlseguin/ccache v2.0.4
go get github.com/karlseguin/ccache/[email protected]: github.com/karlseguin/[email protected]: invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v2

This is because gomodules major versions >=v2 need to have the version in the module path. In this case, the module path in go.mod should be github.com/karlseguin/ccache/v2. Details here.

from ccache.

So I pushed:
937ca29

if I create a new version, it should be all good? (I realize I should know this, but I have little desire to spend time understanding how Go finally decided to do this)

from ccache.

Yes, this should work. Please create a new version from this. Thanks.

from ccache.

Thanks @karlseguin for the fast response time 😄

It's not required for the module name to be changed (adding the /v2 suffix). Go modules can find the v2.x.x versions using the original module path.

Of course, adding the /v2 suffix to the module name, as you did in 937ca29, is the recommended way to go as the Go team is concerned, so I think this what the right call.

Now the examples in the README are wrong because they point to the "plain" v1 module. All imports and install instructions should be changed so they use github.com/karlseguin/ccache/v2 module path.

from ccache.