bundle deps

README.md

@@ -19,12 +19,12 @@ jobs:
   ply:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - uses: actions/setup-node@v1
+    - uses: actions/checkout@v3
+    - uses: actions/setup-node@v3
       with:
         node-version: '16.x'
     - run: npm install
-    - uses: ply-ct/ply-action@v1.2.1
+    - uses: ply-ct/ply-action@v2
 ```
 This example runs all Ply tests and fails if they don't succeed.
 
@@ -44,7 +44,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.2.1
+    - uses: ply-ct/ply-action@v2
       with: 
         github-token: ${{ secrets.MY_GITHUB_TOKEN }}
         badge-branch: badge
@@ -62,7 +62,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.2.1
+    - uses: ply-ct/ply-action@v2
       with: 
         ply-path: node_modules/ply-ct/dist
         result-file: test/api/results/actual/ply-results.json        

package.json

@@ -1,6 +1,6 @@
 {
   "name": "ply-action",
-  "version": "1.2.1",
+  "version": "2.0.1",
   "description": "Ply GitHub Action",
   "main": "index.js",
   "keywords": [
@@ -16,7 +16,7 @@
   },
   "scripts": {
     "lint": "eslint src",
-    "build": "tsc && ncc build -e typescript -e handlebars -e flowbee -e ajv -o dist src/action.ts",
+    "build": "tsc && ncc build -o dist src/action.ts",
     "test": "mocha --require ts-node/register test/**/*.test.ts"
   },
   "devDependencies": {