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
Even though an automated build process has already been defined with github actions, this still isn't enough as it does not include an automated release process, which we need to implement with goreleaser, (Issue 42)
Essentially this is code signing (I wonder if this is only applicable to binaries and not libraries, as in the case of the libary, we don't create a binary, the client does as part of their build process). However, when we tag a release, there is a zipped version of the repo (like a snapshot), perhaps we can sign this.
An AT is more than just a signature. It backs up the signature to describe HOW we
created the signature. Eg an AT may include how an artefact was created, ie what
build command was used to create it.
See: General availability of SLSA3 Generic Generator for GitHub Actions
May also need to look into SLSA Go releaser
Start here
This issue depends on the (automated release process to be defined (go-releaser), see #42
The text was updated successfully, but these errors were encountered: