From adee9a989baa282ee97046aae92f0dcedf1a6dfd Mon Sep 17 00:00:00 2001
From: Jack Green <jack.green@hazelcast.com>
Date: Wed, 8 Jan 2025 09:47:40 +0000
Subject: [PATCH] Revert using our fork of `dockle-action` (#848)

In https://github.com/hazelcast/hazelcast-docker/pull/778 we swapped our
usage of `dockle-action` to our forked version to workaround
https://github.com/goodwithtech/dockle-action/issues/7 - now thhis has
been fixed upstream we can use it again.
---
 .github/workflows/vulnerability_scan_subworkflow.yml | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/vulnerability_scan_subworkflow.yml b/.github/workflows/vulnerability_scan_subworkflow.yml
index 7b1e187c..4064ac92 100644
--- a/.github/workflows/vulnerability_scan_subworkflow.yml
+++ b/.github/workflows/vulnerability_scan_subworkflow.yml
@@ -61,9 +61,8 @@ jobs:
 
       - name: Scan ${{ matrix.image.label }} image by Dockle
         if: always()
-        # Use our fork until https://github.com/goodwithtech/dockle-action/issues/7 is fixed
-        # uses: goodwithtech/dockle-action@main
-        uses: hazelcast/dockle-action/@Upgrade-Dockle-to-`0.4.14`
+        # https://github.com/goodwithtech/dockle-action/releases/tag/v0.4.15
+        uses: goodwithtech/dockle-action@e30e6af832aad6ea7dca2a248d31a85eab6dbd68
         with:
           image: ${{ env.IMAGE_TAG }} 
           format: 'list'