Closed dims closed 3 months ago
do we have multiple modules here? if not let's use toolchain in go.mod and control this 100% in-repo?
do we have multiple modules here? if not let's use toolchain in go.mod and control this 100% in-repo?
only one go.mod here. there's a GO_VERSION in Makefile with a validator hack/ensure-go.sh
to ensure the go version is very specific .. and then the same GO_VERSION env var is used in the dockerfile/cloudbuild as well.
I don't want to do major surgery in this PR @BenTheElder
/lgtm /approve
there's a GO_VERSION in Makefile with a validator hack/ensure-go.sh to ensure the go version is very specific .. and then the same GO_VERSION env var is used in the dockerfile/cloudbuild as well.
toolchain should be respected in all the builds as long as we have a 1.21+ baseline
I don't want to do major surgery in this PR @BenTheElder
fair, but we should really look towards controlling go updates in the repo under test, and we should be able to do that with less effort now.
/retest
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: BenTheElder, dims, krzyzacy
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Docker image fails to build, logs are here.
Pick a newer image docker.io/library/golang:1.22.5-alpine3.20 instead of the missing one!