Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/public-repo-guard.yml
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ jobs:
name: Secrets + content policy
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
- uses: actions/checkout@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09 # v5.1.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

πŸ” Pinned SHA bump should be verified against the upstream v5.1.0 tag

This is a single-line pin bump for actions/checkout inside the security gate workflow. The whole point of the SHA pin (documented in the header comment at .github/workflows/public-repo-guard.yml:9-14) is that the gate cannot be reprogrammed out-of-band, so the new commit SHA fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09 should be confirmed to actually be the commit tagged v5.1.0 in actions/checkout before merging (the comment is only a comment and is not enforced). Nothing else in the workflow changed; the gitleaks version/checksum pinning and content-policy invocation are untouched.

Open in Devin Review

Was this helpful? React with πŸ‘ or πŸ‘Ž to provide feedback.


# gitleaks' GitHub Action requires a paid license for organizations; the CLI
# itself is MIT-licensed and free. Pin the version AND verify the release
Expand Down
Loading