You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we are specifying the go version in several files in the codebase:
go.mod file
Dockerfile base image for the build
.github/workflows/* when we install go through the github actions
Probably somewhere else
To avoid a version misalignments, we should fix the way we set the go version in all the files listed above.
The single source of truth could be the go.mod file, so that the other files can retrieve the go version from there.
Additionally, I'm thinking to remove the building stage from the Dockerfile and use it just to COPY the harpoon artifact inside of it once built outside.
This will simplify the process and make the build unique.
The text was updated successfully, but these errors were encountered:
Currently we are specifying the go version in several files in the codebase:
go.mod
fileDockerfile
base image for the build.github/workflows/*
when we installgo
through the github actionsTo avoid a version misalignments, we should fix the way we set the go version in all the files listed above.
The single source of truth could be the
go.mod
file, so that the other files can retrieve thego
version from there.Additionally, I'm thinking to remove the building stage from the
Dockerfile
and use it just toCOPY
theharpoon
artifact inside of it once built outside.This will simplify the process and make the build unique.
The text was updated successfully, but these errors were encountered: