(fix)[CI] - Allow release-assets.githubusercontent.com in harden runner#782
Merged
christophetd merged 1 commit intomainfrom Mar 25, 2026
Merged
Conversation
christophetd
approved these changes
Mar 25, 2026
christophetd
approved these changes
Mar 25, 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
2 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.
What does this PR do?
Bug Fix:
The staticcheck CI job was failing with exit code 22 (HTTP error) during Go setup: https://github.com/DataDog/stratus-red-team/actions/runs/23483213009/job/68332033526?pr=781#step:10:73
The Harden Runner post-job audit log shows that curl was blocked attempting to reach
release-assets.githubusercontent.com.This domain is called by WillAbides/setup-go-faster (used internally by dominikh/staticcheck-action) to download the Go toolchain binary. My guess is that GitHub silently migrated release asset downloads from
objects.githubusercontent.comtorelease-assets.githubusercontent.comat the CDN level, so the same action code now resolves to a different domain at runtime. It would match this article by the team behind the harden runner: https://www.stepsecurity.io/blog/harden-runner-detects-new-traffic-to-release-assets-githubusercontent-com-across-multiple-customers (but 1 year late 🤷)This PR will have to be force-merged because it won't pass CI as the code used for the test is the code on main and not the code in the branch
Merging this, then rebasing #781 should be enough to fix the CI issue and unblock the other PR