Skip to content

Publish (unsigned for now) SHA-256 checksums on GitHub Releases #345

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

Merged
merged 2 commits into from
May 27, 2025

Conversation

jviotti
Copy link
Member

@jviotti jviotti commented May 26, 2025

See: #344
Signed-off-by: Juan Cruz Viotti [email protected]

@jviotti jviotti force-pushed the checksums-releases branch from c4f9210 to ce1eda0 Compare May 26, 2025 18:28
Signed-off-by: Juan Cruz Viotti <[email protected]>
@jviotti jviotti changed the title Publish (unsigned for now) SHA-512 checksums on GitHub Releases Publish (unsigned for now) SHA-256 checksums on GitHub Releases May 27, 2025
@jviotti
Copy link
Member Author

jviotti commented May 27, 2025

I addressed the comments (thanks @robbat2) and reverted to SHA-256, as I figured I could use this file to automate a bit the Homebrew pushing step too (which requires SHA-256).

@jviotti
Copy link
Member Author

jviotti commented May 27, 2025

Merging this and I'll do a patch release, just to make sure it all works

@jviotti jviotti merged commit 93e0fcb into main May 27, 2025
9 checks passed
@jviotti jviotti deleted the checksums-releases branch May 27, 2025 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants