-
Notifications
You must be signed in to change notification settings - Fork 382
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
checksum of pre built binaries didn't match at v0.24.0 #3121
Comments
Hey, thanks for reporting. We'll look into that! |
It looks like our goreleaser job ran three times at the same time for v0.24.0 because we set three tags: https://github.com/kcp-dev/kcp/actions/workflows/goreleaser.yml, racing to upload artefacts. We will fix that configuration for the next release, I'm following up on #3106. |
I think this is fixed now? |
I suppose it's not really fixed for 0.24, but I don't think we can re-run goreleaser to fix it. It's going to be fixed for the next release though. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale I'll keep this open until we have v0.25.0 released, so a release with correct checksums is available. |
Closing, since v0.25.0 assets are looking fine and therefore there is a version with fixed checksums available. $ sha256sum -c kcp_0.25.0_checksums.txt | grep -v OK | wc -l
0 /close |
@embik: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
https://github.com/kcp-dev/kcp/releases/tag/v0.24.0
Download all assets with GitHub CLI. https://cli.github.com/manual/gh_release_download
Checksum verification with sha256sum fails.
kcp_0.24.0_checksums.txt
The text was updated successfully, but these errors were encountered: