chore: install corepack@latest before enabling to fix signature verification errors

Author: oleksandr-danylchenko

.github/workflows/ci-build-test.yml

@@ -23,9 +23,14 @@ jobs:
           node-version: ${{ matrix.node-version }}
       # setup-node must be called twice to correctly cache corepack-managed npm.
       # See: https://github.com/actions/setup-node/issues/531#issuecomment-3335630863
+      # `corepack@latest` must be installed before `corepack enable npm` to avoid
+      # signature verification errors against rotated npm registry keys.
+      # See: https://github.com/nodejs/corepack/issues/612
       - name: Enable Corepack
         shell: bash
-        run: corepack enable npm
+        run: |
+          npm install --global corepack@latest
+          corepack enable npm
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           cache: npm

.github/workflows/publish-npm.yml

@@ -19,9 +19,14 @@ jobs:
          registry-url: 'https://registry.npmjs.org'
      # setup-node must be called twice to correctly cache corepack-managed npm.
      # See: https://github.com/actions/setup-node/issues/531#issuecomment-3335630863
+     # `corepack@latest` must be installed before `corepack enable npm` to avoid
+     # signature verification errors against rotated npm registry keys.
+     # See: https://github.com/nodejs/corepack/issues/612
      - name: Enable Corepack
        shell: bash
-       run: corepack enable npm
+       run: |
+         npm install --global corepack@latest
+         corepack enable npm
      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
        with:
          cache: npm