feat: add SHA256 hash verification for the installer script - #189
Merged
Conversation
![github-advanced-security[bot]](https://cdn.statically.io/img/avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
art049
force-pushed
the
cod-2243-hash-pin-the-runner-in-the-action
branch
5 times, most recently
from
February 17, 2026 10:13
4629214 to
b545690
Compare
Verify the installer script's SHA256 hash against pinned values before execution, closing a supply chain gap. The expected hashes are stored in .codspeed-runner-installer-hashes.json (sourced from GitHub API digests). - For pinned release versions: download to temp file, verify hash, fail on mismatch or missing hash - For latest/branch/rev: warn that hash verification is not available - Add `skip-hash-check` input to bypass verification if needed - Update bump-runner-version workflow to fetch and store the hash Ref: COD-2243
art049
force-pushed
the
cod-2243-hash-pin-the-runner-in-the-action
branch
from
February 17, 2026 10:21
b545690 to
2a2dd91
Compare
adriencaccia
approved these changes
Feb 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Verify the installer script's SHA256 hash against pinned values before
execution, closing a supply chain gap. The expected hashes are stored in
.codspeed-runner-installer-hashes.json(sourced from GitHub API digests).Changes
Hash verification (
action.yml)latest/branch:/rev:: warn that hash verification is not availableskip-hash-check-warninginput to suppress the warning when hash verification is not availableHash pinning (
.codspeed-runner-installer-hashes.json)Bump runner version workflow (
.github/workflows/bump-runner-version.yml)CI (
.github/workflows/ci.yml)check-installer-hashesjob that runsscripts/check-hashes.shto verify all pinned hashes against GitHub releasestest-recent-pinned-runner-versionsjob that tests the last 5 pinned versions through the actionScripts (
scripts/check-hashes.sh)Ref: COD-2243