From fa9b4f69e8f100e8d62f32862fd5a9385c4100ca Mon Sep 17 00:00:00 2001
From: Nawar Hamo <100778766+nawar-hamo-sonarsource@users.noreply.github.com>
Date: Thu, 3 Aug 2023 20:49:19 +0200
Subject: [PATCH] Bump action version to v2 (#40)

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index fbd38c0..fd6262c 100644
--- a/README.md
+++ b/README.md
@@ -52,7 +52,7 @@ jobs:
         # Disabling shallow clone is recommended for improving relevancy of reporting
         fetch-depth: 0
     - name:  Install sonar-scanner and build-wrapper
-      uses: sonarsource/sonarcloud-github-c-cpp@v1
+      uses: sonarsource/sonarcloud-github-c-cpp@v2
     - name: Run build-wrapper
       run: |
       #here goes your compilation wrapped with build-wrapper; See https://docs.sonarcloud.io/advanced-setup/languages/c-c-objective-c/#analysis-steps-using-build-wrapper for more information
@@ -68,7 +68,7 @@ jobs:
 You can change the `build-wrapper` and `sonar-scanner` installation path by using the optional input `installation-path` like this:
 
 ```yaml
-uses: sonarsource/sonarcloud-github-c-cpp@v1
+uses: sonarsource/sonarcloud-github-c-cpp@v2
 with:
   installation-path: my/custom/directory/path
 ```
@@ -76,7 +76,7 @@ Also, the absolute paths to the installed build-wrapper and sonar-scanner binari
 
 Moreover, by default the action will cache sonar-scanner installation. However, you can disable caching by using the optional input: `cache-binaries` like this:
 ```yaml
-uses: sonarsource/sonarcloud-github-c-cpp@v1
+uses: sonarsource/sonarcloud-github-c-cpp@v2
 with:
   cache-binaries: false
 ```