Which version of Go does v1.27.0 use?

[rootulp]

Context

#118

Question

I'm trying to upgrade our repo to a new Go version (either v1.24.11 or 1.25.5). Neither of those versions have goreleaser-cross Docker images.

I see the most recent release here is v1.27.0 except I don't see a Go version v1.27.0.

The README:

goreleaser-cross/README.md

Lines 15 to 16 in 8ae601d

	Docker images are available on both [GitHub](https://ghcr.io/goreleaser/goreleaser-cross) and [Docker hub](https://hub.docker.com/r/goreleaser/goreleaser-cross). The image's tag version follows Golang
	release so if you use 1.19.4, you are effectively compiling your Go code using Golang at version 1.19.4. The actual version of the other tools installed within the Docker image like `goreleaser` can

makes me think goreleaser-cross v1.27.0 should match Go 1.27. Is that correct?

[caarlos0]

the version of the project does not match the Go version - is just our internal versions.

PS: we're working on improving the release workflows here: https://github.com/goreleaser/goreleaser-cross/pull/116/changes#diff-7326b55c062b0f46fe9e39aace0a25f4515cf206040fb91a6fd2cae839f5e826R4

[rootulp]

the version of the project does not match the Go version

That's confusing considering the line in the README:

goreleaser-cross/README.md

Lines 15 to 16 in 8ae601d

	Docker images are available on both [GitHub](https://ghcr.io/goreleaser/goreleaser-cross) and [Docker hub](https://hub.docker.com/r/goreleaser/goreleaser-cross). The image's tag version follows Golang
	release so if you use 1.19.4, you are effectively compiling your Go code using Golang at version 1.19.4. The actual version of the other tools installed within the Docker image like `goreleaser` can

If the project version doesn't match the Go version, can that line be updated to clarify that the project version is independent of the Go version?

[troian]

something went off i think, it used to be following go versions

[caarlos0]

@troian maybe what we can do is have two different release processes for the base image and for the other image, so maybe we create another project goreleaser/go-cross in which the tags match the Go version

and this repo uses the latest from go-cross + latest goreleaser + etc and follows semver - or maybe follow goreleaser tags to make it easier 🤔

[troian]

@caarlos0 where v1.27.0 came from

i think we should keep goreleaser-cross tags match go versions

[troian]

how about this:
create .goreleaser-base config

in github actions have two stage release, as it only pushes to docker registry, base first followed by main, both base and goreleaser then can use same tag

[caarlos0]

where v1.27.0 came from

probably me trying to push a release out...

[caarlos0]

i think we should keep goreleaser-cross tags match go versions

i'm unsure about it - we have other things than the go in them, which would then lead to having a tag that contains the versions of X other things, which seems overly complicated

[troian]

@caarlos0 lets then remove v1.27.0 and v1.26.0 tags and as well as wipe those docker images.
then tag should follow go release schedule with goreleaser version optionally following.
e.g

goreleaser-cross:v1.25.6
goreleaser-cross:v1.25.6-v2.13.2
goreleaser-cross:v1.25
goreleaser-cross:v1.25-v2.13.2

wdyt

[caarlos0]

removing old versions will break things as well I assume

again, i don't think we should copy go version as our version

[troian]

it has been like this since the beginning up till go1.25.5
idea was that go version from go.mod would allow projects to determine which goreleaser-cross version to use.

it is actually opposite, new versioning breaks integrations in existing projects.

[caarlos0]

oh, ok then
lets do it

[caarlos0]

ok, so, now, we should probably delete these tags (v1.26, v1.27), and then cut a new release?

tag v1.25.5 - probably have to add more info to the tag, e.g. v1.25.5-some-other-thing? Or do we recreate tags when we need to release the same go version with a different version of something else?

[troian]

just need to delete v1.26x and v1.27x, i believe all v1.25 and below are fine

[caarlos0]

yes, but i mean, we'll push v1.25.5 now, when there's a new goreleaser version, what do we do? just push over it? i would argue adding a -v2.x.y (the goreleaser version) to the tag 🤔