`release` workflow is broken

[Pluies]

What happened:

I was trying to cut a v0.6.0 release to bring in bugfixes and dependency updates:

[16:34:30]~/projects/zeitgeist (master) λ git tag v0.6.0
[16:35:07]~/projects/zeitgeist (master) λ git push --tags
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
To github.com:kubernetes-sigs/zeitgeist.git
 * [new tag]         v0.6.0 -> v0.6.0

So far so good.

But the release workflow failed: https://github.com/kubernetes-sigs/zeitgeist/actions/runs/20600070619/job/59163316852

With:

Run actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c
Error: The specified go version file at: go.mod does not exist

Looking at the source for these actions, the main difference I see is that we explicitly set GOPATH on the release job: https://github.com/kubernetes-sigs/zeitgeist/blob/master/.github/workflows/release.yml#L19

But not on the lint job for example: https://github.com/kubernetes-sigs/zeitgeist/blob/master/.github/workflows/lint.yml

I wonder if that's what leading the setup-go action to not find go.mod? 🤔

What you expected to happen:

Release goes through, builds artefacts, etc.

How to reproduce it (as minimally and precisely as possible):

Push a new tag.

Anything else we need to know?:

Environment:

n/a

[Pluies]

cc @cpanato @saschagrunert , I'd happily push a fix here to try, but I'd like to get your input here first to avoid having lots of garbage v0.6.x tags while we fix the release flow 😄

[saschagrunert]

Yeah we should definitely fix that. 👍 It may be possible that you can try out the fix in your fork @Pluies with a modified action. Thank you for working on this! 🙏