Repository navigation
chore(ci): pin gitleaks version in secret-scan (de-flake transient false failure) - #38
Merged
Merged
Conversation
…lse failure) Matches the fix already merged on agentic-os. The unauthenticated api.github.com releases/latest call rate-limits on shared Actions runners, leaving an empty version and a broken download URL that fails CI under set -e -- a transient FALSE failure, not a committed secret. Pinning removes the API call; scan command unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Pins the gitleaks version in
secret-scan.yml, matching the fix already merged on agentic-os. The job resolved the version via an unauthenticatedapi.github.com/releases/latestcall that rate-limits on shared runners -> empty tag -> broken download URL ->curl|tarfails underset -ebefore any scan runs -- a transient FALSE failure, not a committed secret. Pinning removes the API call; scan command unchanged.Generated with Claude Code