Skip to content

Verify checksums of downloaded tools - #102

Open
Frawless wants to merge 1 commit into
frawless/add-zizmorfrom
frawless/verify-checksums
Open

Frawless wants to merge 1 commit into
frawless/add-zizmorfrom
frawless/verify-checksums

Conversation

@Frawless

Copy link
Copy Markdown
Member

Type of Change

  • Enhancement / new feature

Description

The dependency actions downloaded binaries without verifying them. They now check the SHA-256 checksum and fail on a mismatch:

  • syft – syft_<version>_checksums.txt
  • yq – checksums + checksums_hashes_order (works for old versions such as v4.6.3 too)
  • kubectl, minikube, kind – the .sha256 / .sha256sum file published next to each binary
  • ShellCheck – no checksum file is published, so the SHA-256 digest GitHub records for the release asset is used

Helm was already verified by get_helm.sh.

Important

GitHub records asset digests only for releases uploaded since mid-2025, so install-shellcheck now requires ShellCheck 0.11.0 or newer. 0.10.0 was removed from the test matrix and the README notes the minimum.

Checklist

  • Update documentation
  • Write tests
  • Make sure all tests pass
  • Try your changes inside a Kubernetes cluster, not just from unit tests
  • AI assistance was used to create this PR (see the Strimzi AI policy)

Stack created with GitHub Stacks CLI • Give Feedback 💬

@Frawless
Frawless added this pull request to stack #105 November 13, 2026 18:47
@Frawless
Frawless force-pushed the frawless/verify-checksums branch from ef66eeb to 7632729 Compare November 13, 2026 19:15
Signed-off-by: Jakub Stejskal <xstejs24@gmail.com>
@Frawless
Frawless force-pushed the frawless/verify-checksums branch from 7632729 to 738a1e4 Compare November 13, 2026 19:42
@Frawless
Frawless requested a review from a team November 13, 2026 20:27
@Frawless Frawless added this to the 4.0 milestone Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants