Bump tmp and rewire

.github/workflows/npm-publish.yml

@@ -11,7 +11,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-node@v4
         with:
-          node-version: 16
+          node-version: 17
       - run: npm ci
       - run: npm test
 
@@ -22,7 +22,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-node@v4
         with:
-          node-version: 16
+          node-version: 17
           registry-url: https://registry.npmjs.org
       - run: npm ci
       - run: npm publish

.github/workflows/sonar-scanner.yml

@@ -20,10 +20,10 @@ jobs:
           github.event.pull_request.head.repo.full_name == github.repository ||
           github.event_name != 'pull_request_target') }}
         run: echo "Unsecure PR, must be labelled with the 'safe' label, then run the workflow again" && exit 1
-      - name: Use Node.js 16
+      - name: Use Node.js 17
         uses: actions/setup-node@v1
         with:
-          node-version: 16
+          node-version: 17
       - name: Build with npm
         run: |
           npm ci

.github/workflows/test.yml

@@ -15,7 +15,6 @@ jobs:
     strategy:
       matrix:
         node-version:
-          - 16.x
           - 17.x
           - 18.x
           - 19.x

README.md

@@ -28,7 +28,7 @@
 NodeJS library for Mastercard API compliant payload encryption/decryption.
 
 ### Compatibility <a name="compatibility"></a>
-- NodeJS 16+
+- NodeJS 17+
 
 There shouldn't be any Node compatibility issues with this package, but it's a good idea to keep your Node versions up-to-date. It is recommended that you use one of the LTS Node.js releases, or one of the more general recent releases. A Node version manager such as `nvm` (_Mac_ and _Linux_) or `nvm-windows` is a good way to stay on top of this.