facebook / facebook/zstd

Improve and Move Windows Artifact Generation to GitHub Actions

Open
#3,025 3 comments 1 reaction 0 assignees View on GitHub
help wanted release-blocking
Dominant language
C
Stars
27.9k
Forks
2.6k
Avg merge
1d 3h
Merged PRs (30d)
8

Description

It seems like every release we make some kind of little mistake with the naming or contents of the windows artifacts. See #3012 and #3001 recently.

We should improve our automation here. Moving this workflow to GitHub Actions would allow us to publish the artifacts to the release automatically, removing opportunities for error. This would also advance our broad goal of moving contbuild work off of Appveyor and onto GitHub.

It also came up in [discussion](https://github.com/facebook/zstd/issues/3012#issuecomment-1018100769) that it might be convenient to provide both the full existing .zip as well as a binary-only artifact. So this work item should resolve that.

Moving to GitHub Actions would also allow us to sign those artifacts.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.