Use Node.js v20, update dependencies

Author: piotrpepek

.github/workflows/build.yml

@@ -11,7 +11,7 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - run: |
           npm install
       - run: |

.github/workflows/codeql-analysis.yml

@@ -35,7 +35,7 @@ jobs:
 
     steps:
     - name: Checkout repository
-      uses: actions/checkout@v3
+      uses: actions/checkout@v4
 
     # Initializes the CodeQL tools for scanning.
     - name: Initialize CodeQL

.github/workflows/test.yml

@@ -11,7 +11,7 @@ jobs:
   test:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - run: |
           npm install
       - run: |

README.md

@@ -8,7 +8,7 @@ This action enables you to run code analysis with Parasoft C/C++test Standard an
 
 Parasoft C/C++test uses a comprehensive set of analysis techniques, including pattern-based static analysis, dataflow analysis, metrics, code coverage, unit testing, and more, to help you verify code quality and ensure compliance with industry standards, such as MISRA, AUTOSAR, and CERT.
  - Request [a free trial](https://www.parasoft.com/products/parasoft-c-ctest/try/) to receive access to Parasoft C/C++test's features and capabilities.
- - See the [user guide](https://docs.parasoft.com/display/CPPTEST20231) for information about Parasoft C/C++test's capabilities and usage.
+ - See the [user guide](https://docs.parasoft.com/display/CPPTEST20241) for information about Parasoft C/C++test's capabilities and usage.
 
 Please visit the [official Parasoft website](http://www.parasoft.com) for more information about Parasoft C/C++test and other Parasoft products.
 
@@ -35,12 +35,12 @@ We recommend that you run Parasoft C/C++test on a self-hosted rather than GitHub
 ### Adding the Run C/C++test Action to a GitHub Workflow
 Add the `Run C/C++test` action to your workflow to launch code analysis with Parasoft C/C++test.
 
-Depending on the project type and the build system you are using (Make, CMake, etc.), you may need to adjust the workflow to collect the required input data for C/C++test. See the [C/C++test User Guide](https://docs.parasoft.com/display/CPPTEST20231/Running+Static+Analysis+1) for details.
+Depending on the project type and the build system you are using (Make, CMake, etc.), you may need to adjust the workflow to collect the required input data for C/C++test. See the [C/C++test User Guide](https://docs.parasoft.com/display/CPPTEST20241/Running+Static+Analysis+1) for details.
 
 ```yaml
 # Runs code analysis with C/C++test.
 - name: Run C/C++test
-  uses: parasoft/run-cpptest-action@2.0.1
+  uses: parasoft/run-cpptest-action@2.0.2
   with:
     input: build/compile_commands.json
     testConfig: 'builtin://MISRA C 2012'
@@ -57,7 +57,7 @@ To upload the SARIF report to GitHub, modify your workflow by adding the `upload
 # Uploads analysis results in the SARIF format, so that they are displayed as GitHub code scanning alerts.
 - name: Upload results (SARIF)
   if: always()
-  uses: github/codeql-action/upload-sarif@v2
+  uses: github/codeql-action/upload-sarif@v3
   with:
     sarif_file: reports/report.sarif
 ```
@@ -68,7 +68,7 @@ To upload reports in other formats, modify your workflow by adding  the `upload-
 # Uploads an archive that includes all report files (.xml, .html, .sarif).
 - name: Archive reports
   if: always()
-  uses: actions/upload-artifact@v3
+  uses: actions/upload-artifact@v4
   with:
     name: CpptestReports
     path: reports/*.*
@@ -115,7 +115,7 @@ jobs:
 
     # Checks out your repository under $GITHUB_WORKSPACE, so that your job can access it.
     - name: Checkout code
-      uses: actions/checkout@v3
+      uses: actions/checkout@v4
 
     # Configures your CMake project. Be sure the compile_commands.json file is created.
     - name: Configure project
@@ -128,7 +128,7 @@ jobs:
     # Runs code analysis with C/C++test.
     - name: Run C/C++test
       # Use the 'run-cpptest-action' GitHub action.
-      uses: parasoft/run-cpptest-action@2.0.1
+      uses: parasoft/run-cpptest-action@2.0.2
       # Optional parameters for 'run-cpptest-action'.
       with:
         # For CMake-based projects, use a compile_commands.json file as the input for analysis. 
@@ -140,14 +140,14 @@ jobs:
     # Uploads analysis results in the SARIF format, so that they are displayed as GitHub code scanning alerts.
     - name: Upload results (SARIF)
       if: always()
-      uses: github/codeql-action/upload-sarif@v2
+      uses: github/codeql-action/upload-sarif@v3
       with:
         sarif_file: reports/report.sarif
     
     # Uploads an archive that includes all report files (.xml, .html, .sarif).
     - name: Archive reports
       if: always()
-      uses: actions/upload-artifact@v3
+      uses: actions/upload-artifact@v4
       with:
         name: CpptestReports
         path: reports/*.*
@@ -192,7 +192,7 @@ jobs:
 
     # Checks out your repository under $GITHUB_WORKSPACE, so that your job can access it.
     - name: Checkout code
-      uses: actions/checkout@v3
+      uses: actions/checkout@v4
     
     # Builds your Make project using 'cpptesttrace' to collect input data for code analysis.
     # Be sure 'cpptesttrace' is available on $PATH.
@@ -202,7 +202,7 @@ jobs:
     # Runs code analysis with C/C++test.
     - name: Run C/C++test
       # Use the 'run-cpptest-action' GitHub action.
-      uses: parasoft/run-cpptest-action@2.0.1
+      uses: parasoft/run-cpptest-action@2.0.2
       # Uncomment if you are using C/C++test 2020.2 to generate a SARIF report:
       # with:
       #   reportFormat: xml,html,custom
@@ -211,14 +211,14 @@ jobs:
     # Uploads analysis results in the SARIF format, so that they are displayed as GitHub code scanning alerts.
     - name: Upload results (SARIF)
       if: always()
-      uses: github/codeql-action/upload-sarif@v2
+      uses: github/codeql-action/upload-sarif@v3
       with:
         sarif_file: reports/report.sarif
     
     # Uploads an archive that includes all report files (.xml, .html, .sarif).
     - name: Archive reports
       if: always()
-      uses: actions/upload-artifact@v3
+      uses: actions/upload-artifact@v4
       with:
         name: CpptestReports
         path: reports/*.*
@@ -227,7 +227,7 @@ jobs:
 ## Configuring Analysis with C/C++test
 You can configure analysis with Parasoft C/C++test in the following ways:
  - By customizing the `Run C/C++test` action directly in your GitHub workflow. See [Action Parameters](#action-parameters) for a complete list of available parameters.
- - By configuring options in Parasoft C/C++test tool. We recommend creating a `cpptestcli.properties` file that includes all the configuration options and adding the file to C/C++test's working directory  - typically, the root directory of your repository. This allows C/C++test to automatically read all the configuration options from that file. See [Parasoft C/C++test User Guide](https://docs.parasoft.com/display/CPPTEST20231/Configuration+1) for details.
+ - By configuring options in Parasoft C/C++test tool. We recommend creating a `cpptestcli.properties` file that includes all the configuration options and adding the file to C/C++test's working directory  - typically, the root directory of your repository. This allows C/C++test to automatically read all the configuration options from that file. See [Parasoft C/C++test User Guide](https://docs.parasoft.com/display/CPPTEST20241/Configuration+1) for details.
 
 ### Examples
 This section includes practical examples of how the `Run C/C++test` action can be customized directly in the YAML file of your workflow. 
@@ -237,35 +237,35 @@ If `cpptestcli` executable is not on `$PATH`, you can configure the path to the
 
 ```yaml
 - name: Run C/C++test
-  uses: parasoft/run-cpptest-action@2.0.1
+  uses: parasoft/run-cpptest-action@2.0.2
   with:
     installDir: '/opt/parasoft/cpptest'
 ```
 
 #### Defining the Scope of Analysis
-You can configure the `input` parameter to provide the path to a file that defines the scope of analysis (includes a list of source files and compile commands). This parameter depends on the project type and the build system you are using. See the  [C/C++test User Guide](https://docs.parasoft.com/display/CPPTEST20231/Running+Static+Analysis+1) for details.
+You can configure the `input` parameter to provide the path to a file that defines the scope of analysis (includes a list of source files and compile commands). This parameter depends on the project type and the build system you are using. See the  [C/C++test User Guide](https://docs.parasoft.com/display/CPPTEST20241/Running+Static+Analysis+1) for details.
 ```yaml
 - name: Run C/C++test
-  uses: parasoft/run-cpptest-action@2.0.1
+  uses: parasoft/run-cpptest-action@2.0.2
   with:
     input: 'build/compile_commands.json'
 ```
 
 #### Configuring a C/C++test Test Configuration
-Code analysis with C/C++test is performed by using a test configuration - a set of static analysis rules that enforce best coding practices or compliance guidelines. Parasoft C/C++test ships with a wide range of [built-in test configurations](https://docs.parasoft.com/display/CPPTEST20231/Built-in+Test+Configurations).
+Code analysis with C/C++test is performed by using a test configuration - a set of static analysis rules that enforce best coding practices or compliance guidelines. Parasoft C/C++test ships with a wide range of [built-in test configurations](https://docs.parasoft.com/display/CPPTEST20241/Built-in+Test+Configurations).
 To specify a test configuration directly in your workflow, add the `testConfig` parameter to the `Run C/C++test` action and specify the URL of the test configuration you want to use:
 ```yaml
 - name: Run C/C++test
-  uses: parasoft/run-cpptest-action@2.0.1
+  uses: parasoft/run-cpptest-action@2.0.2
   with:
     testConfig: 'builtin://MISRA C 2012'
 ```
 
 #### Configuring a C/C++test Compiler Configuration
-In order to run analysis, C/C++test needs to be configured for a specific compiler. You need to specify the configuration that matches your compiler with the `compilerConfig` parameter. See [Supported Compilers](https://docs.parasoft.com/display/CPPTEST20231/Supported+Compilers) for information about supported compilers.
+In order to run analysis, C/C++test needs to be configured for a specific compiler. You need to specify the configuration that matches your compiler with the `compilerConfig` parameter. See [Supported Compilers](https://docs.parasoft.com/display/CPPTEST20241/Supported+Compilers) for information about supported compilers.
 ```yaml
 - name: Run C/C++test
-  uses: parasoft/run-cpptest-action@2.0.1
+  uses: parasoft/run-cpptest-action@2.0.2
   with:
     compilerConfig: 'clang_10_0'
 ```
@@ -274,7 +274,7 @@ In order to run analysis, C/C++test needs to be configured for a specific compil
 Generating reports in the SARIF format is available in C/C++test since version 2021.1. If you are using an earlier C/C++test version, you need to customize the `Run C/C++test` action to enable generating SARIF reports:
 ```yaml
 - name: Run C/C++test
-  uses: parasoft/run-cpptest-action@2.0.1
+  uses: parasoft/run-cpptest-action@2.0.2
   with:
     reportFormat: xml,html,custom
     additionalParams: '-property report.custom.extension=sarif -property report.custom.xsl.file=${PARASOFT_SARIF_XSL}'
@@ -321,7 +321,7 @@ This section describes how to customize the `Run C/C++test` action to run code a
 Use the `commandLinePattern` parameter to modify the command line for `cpptestcli` executable. The command line pattern depends on your project and the setup of the workspace. Example:
 ```yaml
 - name: Run C/C++test
-  uses: parasoft/run-cpptest-action@2.0.1
+  uses: parasoft/run-cpptest-action@2.0.2
   with:
     # C/C++test workspace will be created in '../workspace'.
     # C/C++test will create a new project based on the provided .bdf file.
@@ -333,7 +333,7 @@ Note: The `compilerConfig` and `reportFormat` action parameters are not directly
 Create a `config.properties` file with additional configuration options for C/C++test Professional, such as reporting options, compiler configuration etc. Then pass the configuration file to `cpptestcli` with the `-localsettings config.properties` option:
 ```yaml
 - name: Run C/C++test
-  uses: parasoft/run-cpptest-action@2.0.1
+  uses: parasoft/run-cpptest-action@2.0.2
   with:
     # C/C++test will use options from 'config.properties'.
     additionalParams: '-localsettings config.properties'

action.yml

@@ -41,5 +41,5 @@ inputs:
     required: false 
     default: '${cpptestcli} -compiler "${compilerConfig}" -config "${testConfig}" -property report.format=${reportFormat} -report "${reportDir}" -module . -input "${input}" ${additionalParams}'
 runs:
-  using: 'node16'
+  using: 'node20'
   main: 'dist/index.js'