Request for checksums on releases

[Futurile]

It would be useful for the sources to have checksums so that packagers/distributions that redistribute can check the validity of the release artifacts.

You did this for the recent obs-source-copy 0.3.0, I guess because there was a 'xz'' archive. Providing a checksum for the original 'Source Code' archive would also be fine.

[exeldro]

The checksums on that source copy release are provided by GitHub. I did nothing to add them.

[Futurile]

It seems that for obs-source-copy an "xz" archive was created (which has a checksum), but an "xz" was not created for obs-source-copy. Do you know why that is?

The two push.yml files look exactly same to me - but I'm not that familiar with the release publishing workflow.

[exeldro]

I usually remove the xz archive from the release as the GitHub release has a source download option and I don't see the need for 2 source download options

[Futurile]

Understood. I can't find any automated way for you to checksum the 'Source' file using the GitHub release API. Every project I've looked at which has checksums on a source file is leaving the xz archive. So I think you shouldn't delete the xz archive - it uses up space, but it adds a checksum and that's useful for downstream packagers.

Alternatively, adding a GitHub Action to generate checksums on everything.