Uploaded Ubuntu 16, SLES12.
$ cat clang+llvm-11.0.1-x86_64-linux-sles12.4.tar.xz.sha256
clang+llvm-11.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz.sha256
77cd59cf6f932cf2b3c9a68789d1bd3f7ba9f471a28f6ba25e25deb1a0806e0d
clang+llvm-11.0.1-x86_64-linux-sles12.4.tar.xz
67f18660231d7dd09dc93502f712613247
Hi,
I would like to automate the signing of some of the release files we
upload to the release page, starting with the source tarballs. My
initial goal is to have a CI job that automatically creates, signs, and
uploads the source tarballs, whenever a new release is tagged. I would
also like
On 1/12/21 9:22 PM, Deep Majumder wrote:
Hi Tom,
Although I am new to the community, I think this a great idea. One
question I have is how would the project key be securely stored. (Like
where to store it and how to prevent leaks, I believe GitHub has a
secrets feature. Would something similar
