chore: Fix release process by upgrading to node==18 because of Semantic Release requirements

Signed-off-by: Danny Chiao <[email protected]>

Author: adchia

.github/workflows/release.yml

@@ -31,7 +31,8 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v2
         with:
-          node-version: '16'
+          node-version: '18.x'
+          registry-url: 'https://registry.npmjs.org'
       - name: Release (Dry Run)
         id: get_versions
         run: |
@@ -56,7 +57,7 @@ jobs:
       - uses: actions/checkout@v2
       - uses: actions/setup-node@v2
         with:
-          node-version: '17.x'
+          node-version: '18.x'
           registry-url: 'https://registry.npmjs.org'
       - name: Bump file versions
         run: python ./infra/scripts/release/bump_file_versions.py ${CURRENT_VERSION} ${NEXT_VERSION}
@@ -98,7 +99,7 @@ jobs:
       - uses: actions/checkout@v2
       - uses: actions/setup-node@v2
         with:
-          node-version: '17.x'
+          node-version: '18.x'
           registry-url: 'https://registry.npmjs.org'
       - name: Bump file versions (temporarily for Web UI publish)
         run: python ./infra/scripts/release/bump_file_versions.py ${CURRENT_VERSION} ${NEXT_VERSION}
@@ -134,7 +135,8 @@ jobs:
     - name: Setup Node.js
       uses: actions/setup-node@v2
       with:
-        node-version: '16'
+        node-version: '18.x'
+        registry-url: 'https://registry.npmjs.org'
     - name: Set up Homebrew
       id: set-up-homebrew
       uses: Homebrew/actions/setup-homebrew@master