v0.64.0 source tarball checksum has been changed
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 47
- Forks
- 142
- Avg merge
- 21h 19m
- Merged PRs (30d)
- 9
Description
Hello, this is a homebrew maintainer and I have noticed that the checksum of source tarball is changed.
-da817547c5f2992d52abe7c13be6d6d7c56535184392aa76739a46ad5978b2c6
+0df73b37235cac974a8a05aa746477980cb3fdad36e30eca1190a3c540e2afdb
Not sure what happen, but anyway I just want to make sure the changed one is valid and fine to use.
Can you check?
Thanks,
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the v0.64.0 source tarball and its release or packaging process, then reproduce both checksum calculations for the reported artifact. Verify which checksum matches the officially published source and document the cause and resolution; the issue is done when the maintainer confirms the valid checksum or corrects the release artifact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100