feat: add action pin policy to scanner#30
Conversation
c475557 to
a7a63ed
Compare
grandizzy
left a comment
There was a problem hiding this comment.
ty! the full-SHA enforcement duplicates zizmor / scan GH action, atm only minimum-age checking (7 days old) is different which we coul fold in existing one?
|
@grandizzy good point, rescoped pr fd2f625, ptal :) |
grandizzy
left a comment
There was a problem hiding this comment.
Please check the inline finding.
|
Hi @grandizzy — your changes-requested review was detected by Voight-Kampff, but you rejected the approval request. Your review did not count toward this PR. The prompt was canceled. This request was for head Re-submit the review and complete the new Voight-Kampff prompt if you want this review to count. |
grandizzy
left a comment
There was a problem hiding this comment.
The Pinact integration and read-only permissions look correct, but the new regression test currently fails because it retains the deliberately broken fixture. One inline blocker; no other findings.
|
Hi @grandizzy — your changes-requested review was detected by Voight-Kampff, but you rejected the approval request. Your review did not count toward this PR. The prompt was canceled. This request was for head Re-submit the review and complete the new Voight-Kampff prompt if you want this review to count. |
Extends the existing
scan-github-actionsworkflow with opt-in pinact policy checks for minimum release age and version comments.Existing scanner callers remain unchanged because pinact defaults to disabled. Callers can enable it with
pinact: true, retain repository-local.pinact.yamlexceptions, and run the policy in the scanner’s existing checkout and job.Validation
actionlintv1.7.12git diff --checkCloses OSS-542