would it make sense for versioning to be committed

[gedw99]

Maybe i have got this wrong but anyway.

I tend to use go install x.y.z@tag cause it works so well these days, but i dont get version info because its NOT in the golang code that is tagged.

go install github.com/oligot/go-mod-upgrade@v0.6.2

which go-mod-upgrade
/Users/apple/workspace/go/bin/go-mod-upgrade

 go-mod-upgrade --version
go-mod-upgrade version=(undefined) commit=(undefined) date=(undefined)

The solution is to have a version.go file that always has the correct version.

goreleaser will just overwrite it with the same value during CI i expect ?

What ya think ?

[gedw99]

here is an example: https://github.com/alda-lang/alda/blob/master/client/gen/version/main.go

[oligot]

Hi,

I just tested it with goreleaser and here is what I get:

> go install github.com/goreleaser/goreleaser@v1.1.0
> goreleaser --version
goreleaser version dev
module version: v1.1.0, checksum: h1:YySqqYTX9kxRU0e/fGQrhivXk8/zD4iUOlL7h0I2gBk=

https://goreleaser.com

So, this is clearly doable 😉

[gedw99]

nice example !

https://github.com/goreleaser/goreleaser/blob/main/main.go#L29
https://github.com/goreleaser/goreleaser/blob/main/main_test.go#L9

He uses a Task, instead of make file and its here to kick off:
https://github.com/goreleaser/goreleaser/blob/main/Taskfile.yml#L30

[oligot]

This now works in version 0.7.0:

> go install github.com/oligot/go-mod-upgrade@v0.7.0
> go-mod-upgrade --version
go-mod-upgrade version dev
module version: v0.7.0

[gedw99]

thanks @oligot works great for me too.