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
It was identified that our release process which uses goreleaser does not define the version. Historically it has been "latest". Additionally historically the release build has been on a developers dev box. This additionally challenges the repeatability of the release (indeterministic version of build tools). While the raised issue is the "version" of goreleaser, the real issue to me seems like a repeatable release build chain which includes version of Go, version of goreleaser, version of docker, etc.
Based on that justification, it seems best to build out the release process to be handled through our CI system which will likely require scripts and a build image which will be self-documenting or traceable. We should document anything that falls outside that assumption.
The text was updated successfully, but these errors were encountered:
It was identified that our release process which uses goreleaser does not define the version. Historically it has been "latest". Additionally historically the release build has been on a developers dev box. This additionally challenges the repeatability of the release (indeterministic version of build tools). While the raised issue is the "version" of goreleaser, the real issue to me seems like a repeatable release build chain which includes version of Go, version of goreleaser, version of docker, etc.
Based on that justification, it seems best to build out the release process to be handled through our CI system which will likely require scripts and a build image which will be self-documenting or traceable. We should document anything that falls outside that assumption.
The text was updated successfully, but these errors were encountered: