Checksum release archives

[untereiner]

Is your feature request related to a problem? Please describe. For now it is necessary to compute manually the sha256 for each release. For instance when updating a spack recipe.

Describe the solution you'd like Produce the checksum at release step (for example using a github actions like this one: https://github.com/wangzuo/action-release-checksums)

Describe alternatives you've considered compute manually shasum -a 256 fesapi-2.xxx at each new release

Additional context n.a.

[philippeVerney]

I do not really like to rely on non official github actions but I agree with the request. If I can easily do it by myself (is it not jsut one command down the road?), this would be awesome. I'll look at it when time permits.

[philippeVerney]

I just manually added some checksums to 2.9.0.1 to check if this fullfills your need : https://github.com/F2I-Consulting/fesapi/releases/tag/v2.9.0.1

[untereiner]

is it not jsut one command down the road?

Yes it should.

It is ok for me. Could it be done for fespp too ? Thank you @philippeVerney

[philippeVerney]

Could it be done for fespp too ?

DONE https://github.com/F2I-Consulting/fespp/releases/tag/v3.2.0

[philippeVerney]

Very interesting and related discussion : https://github.com/orgs/community/discussions/46034 I don' think it changes our plan but it is clearly important to have it in mind. And, to keep this link somewhere.

[untereiner]

Thanks @philippeVerney, the blog post is also interesting.