Automate checksum file generation for release tarballs
Open
area/build
kind/enhancement
team/build
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
For each release we upload the linux and darwin tarballs as assets, along with checksum files for them.
Add a script/make target similar to one from [build-tooling repo](https://github.com/aws/eks-anywhere-build-tooling/blob/main/build/lib/update_checksums.sh) to generate these checksum files for the release assets
Contributor guide
Research direction
Start by inspecting the repository's release process and the checksum-generation example in build-tooling's update_checksums.sh. Add the requested script or make target so the Linux and Darwin release tarballs each produce checksum files, then verify the generated files alongside the release assets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, shell
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100