1.1.0

README.md

@@ -22,9 +22,9 @@ jobs:
     - uses: actions/checkout@v2
     - uses: actions/setup-node@v1
       with:
-        node-version: '14.x'
+        node-version: '16.x'
     - run: npm install
-    - uses: ply-ct/ply-action@v1.0.4
+    - uses: ply-ct/ply-action@v1.1.0
       with: 
         ply-path: node_modules/ply-ct/dist 
 ```
@@ -46,7 +46,7 @@ able to retrieve their workflow build status. The question mark at the end of th
 ## Private repositories
 Private repositories can use ply-action as in the example above, but to include a badge some additional configuration is needed:
 ```yaml
-    - uses: ply-ct/ply-action@v1.0.4
+    - uses: ply-ct/ply-action@v1.1.0
       with: 
         ply-path: node_modules/ply-ct/dist
         github-token: ${{ secrets.MY_GITHUB_TOKEN }}
@@ -65,7 +65,7 @@ If you've already integrated Ply CLI commands into a GitHub workflow (say with c
 skip Ply test execution altogether, and use ply-action simply to perform a badge commit based on the results of previous Ply CLI run.
 In that case, specify the path to an overall Ply results file created using the `--resultFile` [CLI arg](https://ply-ct.org/ply/topics/config):
 ```yaml
-    - uses: ply-ct/ply-action@v1.0.4
+    - uses: ply-ct/ply-action@v1.1.0
       with: 
         ply-path: node_modules/ply-ct/dist
         result-file: test/api/results/actual/ply-results.json        

action.yaml

@@ -32,6 +32,6 @@ outputs:
   ply-result:
     description: Ply test result summary
 runs:
-  using: node12
+  using: node16
   main: './dist/index.js'