go-vikunja
fix: align go version
We have currently these logs in the ci when calling setup-go, see https://github.com/actions/setup-go/issues/424.
/usr/bin/tar: ../../../go/pkg/mod/golang.org/[email protected]/LICENSE: Cannot open: File exists
/usr/bin/tar: ../../../go/pkg/mod/golang.org/[email protected]/CONTRIBUTING.md: Cannot open: File exists
/usr/bin/tar: ../../../go/pkg/mod/golang.org/[email protected]/README.md: Cannot open: File exists
/usr/bin/tar: ../../../go/pkg/mod/golang.org/[email protected]/lib/time/mkzip.go: Cannot open: File exists
/usr/bin/tar: ../../../go/pkg/mod/golang.org/[email protected]/lib/time/zoneinfo.zip: Cannot open: File exists
/usr/bin/tar: ../../../go/pkg/mod/golang.org/[email protected]/lib/time/update.bash: Cannot open: File exists
/usr/bin/tar: ../../../go/pkg/mod/golang.org/[email protected]/lib/time/README: Cannot open: File exists
/usr/bin/tar: ../../../go/pkg/mod/golang.org/[email protected]/lib/fips140/Makefile: Cannot open: File exists
/usr/bin/tar: ../../../go/pkg/mod/golang.org/[email protected]/lib/fips140/README.md: Cannot open: File exists
/usr/bin/tar: ../../../go/pkg/mod/golang.org/[email protected]/lib/fips140/v1.0.0.zip: Cannot open: File exists
/usr/bin/tar: ../../../go/pkg/mod/golang.org/[email protected]/lib/fips1[40](https://github.com/go-vikunja/vikunja/actions/runs/14217174464/job/39836464695#step:3:41)/fips140.sum: Cannot open: File exists
/usr/bin/tar: ../../../go/pkg/mod/golang.org/[email protected]/lib/wasm/go_js_wasm_exec: Cannot open: File exists
This might be the related issue https://github.com/actions/setup-go?tab=readme-ov-file#getting-go-version-from-the-gomod-file
If I understand this correctly, the go version isn't read out of the go.mod file by default (instead the runner default is used).
@kolaente In order to test this, this needs to re-run, since the caches weren't full in the first run.
Currently I'm not able to trigger that.
Since there is still a cache hit for a newer go version I'm still not sure if this change is working.
@kolaente Could you clear the cache?
@dpschen Done and re-triggered the workflow, we'll see
Well unsure now. Seems like it's still hitting the cache: https://github.com/go-vikunja/vikunja/actions/runs/14217874844/job/39858342713#step:5:24
But it's not matching. Any ideas? Else I guess we'll just dismiss this.
Maybe because the action does not use the version read from go.mod to construct the cache key? That would be a bug in the action.
In any case, I think this is fine. The step runs in 13s, which is pretty fast already.
Do you mean with this change or as it was before. Because how I understand it: the cache is not used, but at the same time the correct go version is used with this PR.