-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
File path in *.sha512 should not be absolute path #9323
Comments
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
Finally, remember to use https://discuss.ipfs.io if you just need general support. |
See ipfs/kubo#9323. This is a darwin release thing because the signature process for macOS means that we recalculate sha512 and cid and we do this using an absolute path so the result includes the path to the file. The fix is to cd to the folder and do it from there.
Possible fix here: ipfs/distributions#1108 |
Confirmed the fix works. Reopening here as this will be applied to Kubo 0.32 so we need to wait until #10547 is closed. |
Checklist
Installation method
third-party binary
Version
No response
Config
No response
Description
The content of kubo_v0.16.0_darwin-arm64.tar.gz.sha512 is wrong.
Expected content
Actual content
I guess this is the absolute path in GitHub Actions, but I think this should be only a file name.
ref.
kubo/.github/workflows/sync-release-assets.yml
Lines 24 to 128 in 199fa47
The text was updated successfully, but these errors were encountered: