feat(ci): implement binary signing w/ GPG+keybase #1210
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- all release binaries will be signed using the GPG key located at https://keybase.io/axelardev TESTED: a sample signing workflow can seen at https://github.com/erain9/container-playground/runs/4797692525?check_suite_focus=true
erain9
requested review from
cgorenflo,
haiyizxx,
jcs47 and
fish-sammy
as code owners
erain9
added a commit
to axelarnetwork/tofnd
that referenced
this pull request
Jan 15, 2022
cgorenflo
approved these changes
Jan 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
All release binaries will be signed using the GPG key located at https://keybase.io/axelardev
Steps to Test
TESTED: a sample signing workflow can seen at https://github.com/erain9/container-playground/runs/4797692525?check_suite_focus=true
Expected Behaviour
All the binaries in the Github Releases will come with their signature files, and can be verified against the key on https://keybase.io/axelardev