From 8ddbde10c452e0e05ace4180e0150640617473eb Mon Sep 17 00:00:00 2001
From: Igor Eulalio <igor.eulalio@sysdig.com>
Date: Tue, 9 Apr 2024 14:38:46 -0300
Subject: [PATCH] chore: bump tag version for examples

---
 README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 922d012..71582ec 100644
--- a/README.md
+++ b/README.md
@@ -129,7 +129,7 @@ You need to assign an ID to the Sysdig Scan Action step, like:
 
     - name: Scan image
       id: scan
-      uses: sysdiglabs/scan-action@v4
+      uses: sysdiglabs/scan-action@v5
       with:
         ...
 ```
@@ -160,7 +160,7 @@ The `if: success() || failure()` option makes sure the SARIF report is uploaded
 
     - name: Scan image
       id: scan
-      uses: sysdiglabs/scan-action@v4
+      uses: sysdiglabs/scan-action@v5
       with:
           image-tag: sysdiglabs/dummy-vuln-app:latest
           sysdig-secure-token: ${{ secrets.SYSDIG_SECURE_TOKEN }}
@@ -179,7 +179,7 @@ The `if: success() || failure()` option makes sure the SARIF report is uploaded
     ...
 
     - name: Scan image
-      uses: sysdiglabs/scan-action@v4
+      uses: sysdiglabs/scan-action@v5
       with:
         image-tag: "sysdiglabs/dummy-vuln-app:latest"
         sysdig-secure-token: ${{ secrets.SYSDIG_SECURE_TOKEN }}
@@ -191,7 +191,7 @@ The `if: success() || failure()` option makes sure the SARIF report is uploaded
     ...
 
     - name: Scan infrastructure
-      uses: sysdiglabs/scan-action@v4
+      uses: sysdiglabs/scan-action@v5
       with:
         sysdig-secure-token: ${{ secrets.SYSDIG_SECURE_TOKEN }}
         cli-scanner-version: 1.9.0