update action version

README.md

@@ -10,7 +10,7 @@ On a GitHub action step add the following entry:
 
 ````yaml
   - name: Executing an oJob
-    uses: openaf/ojob-action@v4
+    uses: openaf/ojob-action@v5
     with:
       # the reference to a local oJob yaml/json file or a remote oJob.io
       ojob: '...' 
@@ -32,7 +32,7 @@ After the first use, in a job, the installation of the OpenAF runtime is reused
       path: /tmp/oaf
 
   - name: Executing an oJob
-    uses: openaf/ojob-action@v4
+    uses: openaf/ojob-action@v5
     with:
       ojob: '...' 
       args: 'key1=value1 key2=value2 ...'
@@ -46,7 +46,7 @@ It's possible to add the oJob YAML definition directly as the action parameters:
 
 ````yaml
   - name: Executing Hello World
-    uses: openaf/ojob-action@v4
+    uses: openaf/ojob-action@v5
     with:
       def : |
         todo:
@@ -69,7 +69,7 @@ If you have a local OpenAF script you can also run directly.
 
 ````yaml
   - name: Executing hello.js
-    uses: openaf/ojob-action@v4
+    uses: openaf/ojob-action@v5
     with:
       oaf : scripts/hello.js
       args: "name=Tiger"
@@ -81,7 +81,7 @@ If necessary, it's also possible to embeed a script directly with _script_:
 
 ````yaml
   - name: Executing hello.js
-    uses: openaf/ojob-action@v4
+    uses: openaf/ojob-action@v5
     with:
       script: |
         var params = processExpr(" ")
@@ -111,7 +111,7 @@ jobs:
     - uses: actions/checkout@v4
 
     - name: Retrieve env variables for testing
-      uses: openaf/ojob-action@v4
+      uses: openaf/ojob-action@v5
       with:
         ojob: 'ojob.io/envs'
 ````
@@ -132,7 +132,7 @@ jobs:
     - uses: actions/checkout@v4
 
     - name: Echo input args for testing
-      uses: openaf/ojob-action@v4
+      uses: openaf/ojob-action@v5
       with:
         ojob: 'ojob.io/echo'
         args: 'abc=123 xyz=abc'
@@ -162,21 +162,21 @@ jobs:
     - uses: actions/checkout@v4
 
     - name: Scan some/image:latest
-      uses: openaf/ojob-action@v4
+      uses: openaf/ojob-action@v5
       with:
         ojob: 'ojob.io/sec/genSecBadge'
         args: 'image=some/image:latest file=.github/sec-latest.svg'
         dist: 'nightly'
 
     - name: Scan some/image:build
-      uses: openaf/ojob-action@v4
+      uses: openaf/ojob-action@v5
       with:
         ojob: 'ojob.io/sec/genSecBadge'
         args: 'image=some/image:build file=.github/sec-build.svg'
         dist: 'nightly'
 
     - name: Add the generated badges 
-      uses: openaf/ojob-action@v4
+      uses: openaf/ojob-action@v5
       env :
         GH_TOKEN: ${{ github.token }}
       with:
@@ -201,7 +201,7 @@ jobs:
     - uses: actions/checkout@v4
 
     - name: Running get version
-      uses: openaf/ojob-action@v4
+      uses: openaf/ojob-action@v5
       with:
         def : |
           todo:

USES.md

@@ -15,7 +15,7 @@ steps:
 - name: Commit changes
   env :
     GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-  uses: openaf/ojob-action@v4
+  uses: openaf/ojob-action@v5
     with:
       ojob: 'ojob.io/git/hub/contentIn'
       args: 'message="Update\ files" title="Automated\ update\ PR\" paths="README.md,changed/path/"'
@@ -31,7 +31,7 @@ This oJob.io job will use a docker container to scan the provided image with Tri
 ````yaml
 steps:
 - name: Scan latest
-  uses: openaf/ojob-action@v4
+  uses: openaf/ojob-action@v5
   with:
     ojob: 'ojob.io/sec/genSecBadge'
     args: 'image=openaf/oaf:latest file=.github/sec-latest.svg reportFile=.github/sec-latest.yaml'
@@ -45,7 +45,7 @@ You can also convert the YAML results into a markdown with a fixed-width tree di
 ````yaml
 steps:
 - name: Generate sec-latest.md
-  uses: openaf/ojob-action@v4
+  uses: openaf/ojob-action@v5
   with:
     ojob: 'ojob.io/util/toMDTree'
     args: 'inputFile=.github/sec-latest.yaml file=.github/sec-latest.md'
@@ -68,7 +68,7 @@ You can also write a quick oJob definition to generate a badge with custom value
 
 ````yaml
   - name: Update version badge
-    uses: openaf/ojob-action@v4
+    uses: openaf/ojob-action@v5
     with:
       def : |
         todo: