ci: bump pinned cfdude/.github security workflows to 8931286e - #73
Merged
Conversation
Stays SHA-pinned (per the convention documented in this file) -- moves the pin to the hardened workflow rather than switching to a moving @main ref. What the new SHA brings: - timeout-minutes on every job (check-archived 5m, trivy 15m, semgrep 20m). Previously unset, so a wedged step inherited the Actions 6-hour default. This is the CI half of an unbounded-hang class that blocked local commits on 2026-07-30, when a wedged docker credential helper made Trivy block forever refreshing its vulnerability DB. Because these calls are pinned to an immutable SHA they did NOT pick the fix up the way the ~100 @main callers did -- this is the deliberate re-check the comment in this file asks for. Scan behaviour, severity filters, and exit-code semantics are unchanged.
cfdude
force-pushed
the
ci/bump-github-workflow-pin-8931286e
branch
from
July 30, 2026 18:34
13518df to
ac5be9c
Compare
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.
Stays SHA-pinned (per the convention documented in
security.yml) — this moves the pin to the hardened workflow rather than switching to a moving@mainref.What the new SHA brings
timeout-minuteson every job (check-archived 5m, trivy 15m, semgrep 20m). Previously unset, so a wedged step inherited the GitHub Actions 6-hour default.This is the CI half of an unbounded-hang class that blocked local commits on 2026-07-30, when a wedged docker credential helper made Trivy block indefinitely while refreshing its vulnerability DB (two commit attempts were killed at 7 and 10 minutes).
Why this repo needed a manual bump
These calls are pinned to an immutable SHA, so they did not pick the fix up the way the ~100
@maincallers across cfdude/onvexai did. This is the deliberate re-check thatsecurity.yml's own comment asks for.Scan behaviour, severity filters, and exit-code semantics are unchanged.
https://claude.ai/code/session_01ML3EF1HrxrwToger26x66r