From d1cb1386f2a6744eb6c0dde23eb01df391d3cbb3 Mon Sep 17 00:00:00 2001
From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com>
Date: Fri, 12 Jul 2024 07:34:01 +0000
Subject: [PATCH] chore(deps): update snyk/actions digest to 640e317

---
 .github/workflows/snyk-security-scan.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/snyk-security-scan.yml b/.github/workflows/snyk-security-scan.yml
index 7d55b82..023ceaa 100644
--- a/.github/workflows/snyk-security-scan.yml
+++ b/.github/workflows/snyk-security-scan.yml
@@ -47,7 +47,7 @@ jobs:
       - name: Set up Snyk CLI to check for security issues
         # Snyk can be used to break the build when it detects security issues.
         # In this case we want to upload the SAST issues to GitHub Code Scanning
-        uses: snyk/actions/setup@d406fd286b663eb8c6f8adcced4f7bcd199c0a3f
+        uses: snyk/actions/setup@640e31719aac3e44867d239dc86c20c3e34c8e4f
         # For Snyk Open Source you must first set up the development environment for your application's dependencies
         # For example for Node
         #- uses: actions/setup-node@v3