[Go SDK] Package versions aren't in sync with recent releases

[cdecoux]

The interpreted versions of the Go SDK package, github.com/looker-open-source/sdk-codegen/go, are not getting updated with the new releases being tagged. Go seems to think that v0.0.2 is the latest version, e.g:

➜  cat go.mod 
module example.com

go 1.22.2
➜  go get github.com/looker-open-source/sdk-codegen/go       
go: added github.com/looker-open-source/sdk-codegen/go v0.0.2
➜  cat go.mod 
module example.com

go 1.22.2

require github.com/looker-open-source/sdk-codegen/go v0.0.2 // indirect

Another example is shown on https://pkg.go.dev/github.com/looker-open-source/sdk-codegen/go?tab=versions, which only show two versions. It looks like these align with the tags go/v0.0.1 and go/v0.0.2

Perhaps removing those go tags would help. I guess it checks the go tree as a priority, but otherwise I think this repo needs to keep a vanilla vX.Y.Z semantic version tag up to date (i.e, I think the next latest version would be v21.0.10 as the versions after that seem to be tagging it like sdk-vX.Y.Z)

[drstrangelooker]

I actually ran into this yesterday.

I'm researching the right way to tag this.

[drstrangelooker]

Still working on this, but in the meantime you can put github.com/looker-open-source/sdk-codegen/go v0.0.0-20241202185240-d88021950929 into your go.mod file.