Skip to content

ci: add checksum and signing support for release binaries#497

Open
vinayakjeet wants to merge 1 commit intourunc-dev:mainfrom
vinayakjeet:ci/checksum-and-signing
Open

ci: add checksum and signing support for release binaries#497
vinayakjeet wants to merge 1 commit intourunc-dev:mainfrom
vinayakjeet:ci/checksum-and-signing

Conversation

@vinayakjeet
Copy link
Contributor

@vinayakjeet vinayakjeet commented Feb 19, 2026

Resolves: #199

Description

Add SHA256 checksum generation and cosign keyless signing to the release pipeline.
This generates .sha256, .sig, and .crt files for all release binaries only during releases, attaches them to GitHub Releases for verifiable artifacts, and removes legacy S3 upload workflows to keep daily CI fast.

Related issues

How was this tested?

  • Build and lint

LLM usage

None

Checklist

  • I have read the contribution guide.
  • The linter passes locally (make lint).
  • The e2e tests of at least one tool pass locally (make test_ctr, make test_nerdctl, make test_docker, make test_crictl).
  • If LLMs were used: I have read the llm policy.
@netlify
Copy link

netlify bot commented Feb 19, 2026

Deploy Preview for urunc canceled.

Name Link
🔨 Latest commit 57f1ae5
🔍 Latest deploy log https://app.netlify.com/projects/urunc/deploys/6996dacc902d83000853fd28
@vinayakjeet vinayakjeet force-pushed the ci/checksum-and-signing branch from 8e0b067 to 1458aa4 Compare February 19, 2026 06:52
@cmainas
Copy link
Contributor

cmainas commented Feb 19, 2026

Hello @vinayakjeet ,

thank you for this PR, but why are you removing the S3 upload, it is used for a completely different purpose.

@vinayakjeet vinayakjeet force-pushed the ci/checksum-and-signing branch from 1458aa4 to 57f1ae5 Compare February 19, 2026 09:41
@vinayakjeet
Copy link
Contributor Author

@cmainas Apologies for the confusion — I misread the scope and incorrectly removed the S3 upload. I've reverted that, the PR now only adds SHA256 checksums and cosign signing to release-trigger.yaml, leaving the S3 pipeline untouched. Ready for review .Thanks

Add SHA256 checksum generation and cosign keyless signing to
release-trigger.yaml. Checksums and signatures are generated
at release time only, keeping the build pipeline fast and
release artifacts verifiable.

- Generate .sha256 checksum files for all release binaries
- Sign binaries with cosign using GitHub OIDC (keyless)
- Include .sha256, .sig, and .crt files in GitHub Releases

Resolves: urunc-dev#199

Signed-off-by: vinayakjeet <vinayakjeetog@gmail.com>
@cmainas
Copy link
Contributor

cmainas commented Feb 19, 2026

@ananos please take a look since you have much more experience with cosign

@cmainas cmainas requested a review from ananos February 19, 2026 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants