Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add GitHub Action to Automatically Publish Release Tarballs #2535

Merged
merged 4 commits into from
Mar 15, 2021

Conversation

felixhandte
Copy link
Contributor

@felixhandte felixhandte commented Mar 12, 2021

This PR introduces a GitHub action that is triggered on release creation, which creates the release tarball, compresses it, hashes it, signs it, and attaches all of those files to the release.

Here's an example invocation on my repo:

Screenshot from 2021-03-12 17-33-48

I wanted to also generate the windows artifacts but windows is hard and I gave up.

Because this PR signs the artifacts when a key is provided, this is one step towards addressing #2520.

This commit introduces a GitHub action that is triggered on release creation,
which creates the release tarball, compresses it, hashes it, signs it, and
attaches all of those files to the release.
@terrelln
Copy link
Contributor

This looks good to me! I don't have a strong preference on the tarball names. As long as we aren't changing the old names, it shouldn't be a huge deal to add v. But, I guess I'd very slightly prefer keeping zstd-1.4.9.

When the tag is `v1.2.3`, name the artifacts `zstd-1.2.3.tar*` rather than
`zstd-v1.2.3.tar*`. When the tag doesn't match, use the full tag.
@felixhandte felixhandte force-pushed the gha-release-artifacts branch from d47ae02 to 2303306 Compare March 15, 2021 16:39
@felixhandte felixhandte force-pushed the gha-release-artifacts branch from 2303306 to d2b7f2e Compare March 15, 2021 16:52
@felixhandte felixhandte merged commit d1a6d08 into facebook:dev Mar 15, 2021
@mohe2015
Copy link

I think this is fine as an MVP but I really don't like it that this seems to do signing on Github's servers. The keys should be guarded as much as possible - some people even use hardware security keys.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants