I see that Travis has a workflow for encrypting a files, here.
My use case is slightly simpler, I just want to generate a signature for a file that has been built on Travis-CI. Say:
hello-0.0.1-a.bin.asc
hello-0.0.1-a.bin
pubkey.gpg
<or> hello-0.0.1-a.pub
In this case hello-0.0.1-a.bin is created by a Travis build, and will be pushed to Github as a release.
Likewise the signature must also be pushed to Github as a release (i.e. under the same tag).
I don't strongly care (i.e. not a deal breaker) if the private/public key-pair is unique to that build. But it would be ideal if the private/public key-pair is shared between builds.
Appreciate and hints tips or incantations.