We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
it seems to be a good practice, to verify checksums of files that have been downloaded. It would be great, if you could provide those checksums as part of your release workflow. Here are two examples of other GitHub projects that do just that: https://github.com/firecracker-microvm/firecracker/releases https://github.com/containerd/containerd/releases
I don't really care if you use sha512 or sha256.
If you provide those checksums, than renoavte would be able to update files, that automatically download your source archive.
We could make use of this in our Dockerfile, as we currently have to update the version and checksum manually.
There seems to be a Github Action that does just that, although I have never used it myself.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion. I'll try and look into it when I have a chance.
Sorry, something went wrong.
No branches or pull requests
Hello,
it seems to be a good practice, to verify checksums of files that have been downloaded. It would be great, if you could provide those checksums as part of your release workflow.
Here are two examples of other GitHub projects that do just that:
https://github.com/firecracker-microvm/firecracker/releases
https://github.com/containerd/containerd/releases
I don't really care if you use sha512 or sha256.
If you provide those checksums, than renoavte would be able to update files, that automatically download your source archive.
We could make use of this in our Dockerfile, as we currently have to update the version and checksum manually.
There seems to be a Github Action that does just that, although I have never used it myself.
The text was updated successfully, but these errors were encountered: