opencontainers / opencontainers/runc
Release binaries should be built on the CI, not on a maintainer's host
Open
Nobody has claimed this yet.
area/ci
enhancement
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
The binaries should be built on the CI with GitHub Attestations (https://github.com/actions/attest), not on a maintainer's laptop.
The builds should be also reproducible (https://reproducible-builds.org).
Contributor guide
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 reviewing the GitHub Attest documentation and the reproducible-builds guidance linked in the issue, then inspect the repository's existing CI and release process. Done means release binaries are built in CI, attested with GitHub Attestations, and reproducible rather than built on a maintainer's host.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- build-system, release, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100