-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
RFE: please start making github releases #1547
Comments
We're currently not looking into this. When we previously looked into it, Github releases regenerated the tarballs and the checksum was not guaranteed to match. Since we value verification and authentication, it didn't seem like a good solution. |
This RFE has nothing to do with any tar balls. |
Thank you for bringing this to our attention! We're currently looking into this. |
Thank you very much 👍 😄 Few links which I've collected rising this kind of RFEs recently which may help you. Description about how to add create gh release using gh worflows/actions jbms/sphinx-immaterial#281 (comment) |
This sounds like someone was checksumming a file then uploading it as artefact. This is not what you do with releases. https://github.com/userdocs/iperf3-static/releases/tag/3.15 Just use gh cli https://cli.github.com/manual/gh_release_upload There is nothing complicated about releasing iperf3 binaries via github releases. |
We already started using github releases, starting with our last release and including the new release today, but thank you for your help. We definitely appreciate the original poster bringing it to our attention. |
Is it possible next time on release new version make the github release to have entry on https://github.com/esnet/iperf/releases? 🤔
I'm asking because only on make gh release is spread notification about new release to those who have set watch->releases.
More about gh releases is possible to find on
https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
The text was updated successfully, but these errors were encountered: