Is your feature request related to a problem? Please describe.

The checksum feature currently lumps all the checksums for a release into a single checksums.txt file. If we're using automation to download and verify our release binaries, some tools may not be able to parse the checksums.txt file correctly.

For our use-case, we're using gorelease to build and release a Vault plugin. To register the vault plugin, we need to pass the binary and sha256 has to vault: https://developer.hashicorp.com/vault/docs/plugins/plugin-architecture#plugin-catalog Because the hash is store in checksums.txt, rather than in an individual checksum file per file, it is a bit hard to automate.

Describe the solution you'd like

I would like to be able to produce checksums for each released asset individually in self-contained files.
For example, if my release has 2 artifacts, I'd like to have 2 checksums:

• my_plugin.exe
• my_plugin.exe.sha256
• my_plugin_linux
• my_plugin_linux.sha256

Describe alternatives you've considered

None

Search

• I did search for other open and closed issues before opening this

Supporter

• I am a sponsor or a Pro customer

Code of Conduct

• I agree to follow this project's Code of Conduct

Additional context

No response