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, the CI only signs binary artifacts if they correspond to a full-blown release. (See here). I propose that we instead sign binary artifacts on every commit, not just releases, for the following reasons:
Always signing binaries gives us more confidence that the CI process is working correctly.
If something goes wrong with a release, it's handy to be able to download a binary artifact from an adjacent commit and have everything signed already.
The .sig files that are produced are incredibly small (~500 bytes), so there no real file size penalty for including them.
Currently, the CI only signs binary artifacts if they correspond to a full-blown release. (See here). I propose that we instead sign binary artifacts on every commit, not just releases, for the following reasons:
.sig
files that are produced are incredibly small (~500 bytes), so there no real file size penalty for including them.See also GaloisInc/saw-script#1669.
The text was updated successfully, but these errors were encountered: