From 2a50cb353cef44550dfbec6e87aa0c16676ea1b6 Mon Sep 17 00:00:00 2001 From: Marguerite Martinez Date: Wed, 2 Sep 2026 08:51:14 -0400 Subject: [PATCH] Restore the @main-vs-pinned-sha rationale comment Per Grant's review feedback, matching evergreen#30007. Co-Authored-By: Claude Sonnet 5 --- .github/workflows/socket-basics.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/workflows/socket-basics.yml b/.github/workflows/socket-basics.yml index 1cd8574..5ddf328 100644 --- a/.github/workflows/socket-basics.yml +++ b/.github/workflows/socket-basics.yml @@ -6,6 +6,10 @@ on: jobs: socket-basics-security-scan: + # We intentionally run this shared action from @main, not from a pinned sha + # this is because we control the ynab-sast-scanner repo, so there is not a significant risk of malicious changes being pushed. + # Plus, the shared action does use pinned dependencies, and so will be updated fairly often. When we do that, we do not + # want to have to update the sha in every repo that uses this shared action, before such updates apply. uses: ynab/ynab-sast-scanner/.github/workflows/socket-basics.yml@main secrets: SOCKET_SECURITY_API_KEY: ${{ secrets.SOCKET_SECURITY_API_KEY }}