fix(node version on runner): node16 to node18 (#49)

* Added functionality to remove the current user as a watcher on the new ticket

* added code to set priority based on severity

* added axios to support removing watchers from tickets (jira-client does not include)

* clean up

* Added createdAt field to our findings and a filter to only create Jira issues if the finding has existed for longer than 24 hours

* update output to prepare for sending to slack via GitHub action

* Jira needs priority ID as a string in an object

* update dependencies

* Update macpro-security-hub-sync.ts

* Update macpro-security-hub-sync.ts

* updates based on PR feedback

* upgrade from node 16 to 18

.github/workflows/release.yml

@@ -18,7 +18,7 @@ jobs:
       - uses: actions/checkout@v3
       - uses: actions/setup-node@v3
         with:
-          node-version: 16
+          node-version: 18
       - run: npm ci
       - run: npm run build
       - run: npx semantic-release

.github/workflows/test.yml

@@ -20,6 +20,6 @@ jobs:
       - uses: actions/checkout@v3
       - uses: actions/setup-node@v3
         with:
-          node-version: 16
+          node-version: 18
       - run: npm ci
       - run: npm run test

.github/workflows/unit-tests.yml

@@ -18,7 +18,7 @@ jobs:
       - uses: actions/checkout@v3
       - uses: actions/setup-node@v3
         with:
-          node-version: 16
+          node-version: 18
       - run: npm install
       - run: npm run coverage
       - name: publish test coverage to code climate

examples/.github/workflows/security-hub-jira-sync.yml

@@ -21,11 +21,11 @@ jobs:
       - name: Install Node
         uses: actions/setup-node@v3
         with:
-          node-version: 16
+          node-version: 18
 
       # AWS credentials must be provided to get findings from security hub; how you inject credentials can vary.
       - name: Configure AWS credentials
-        uses: aws-actions/configure-aws-credentials@v1-node16
+        uses: aws-actions/configure-aws-credentials@v2
         with:
           role-to-assume: ${{ secrets.AWS_OIDC_ROLE_TO_ASSUME }}
           aws-region: us-east-1