From 123ceba49e1f6fea0c5558cbe7d16b8280a3a16f Mon Sep 17 00:00:00 2001 From: Robert DeRienzo Date: Fri, 9 Oct 2026 19:49:42 +0000 Subject: [PATCH] ci: publish on Node 24 instead of upgrading npm Sonar flagged `npm install -g npm@11` in the publish job: it runs lifecycle scripts and installs an unpinned version. Node 24 releases bundle npm 11.19 (>= 11.15.0, needed for `npm stage publish`), so use Node 24 and drop the install. check-latest keeps the runner from using an older cached Node 24. --- .github/workflows/release-please.yml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.github/workflows/release-please.yml b/.github/workflows/release-please.yml index 88541de..82b190f 100644 --- a/.github/workflows/release-please.yml +++ b/.github/workflows/release-please.yml @@ -38,13 +38,14 @@ jobs: - uses: actions/checkout@v7 with: ref: ${{ inputs.tag || github.sha }} + # Trusted publishing allows only `npm stage publish`, which needs npm >= 11.15.0. + # Current Node 24 releases bundle npm 11.19; check-latest skips an older cached Node 24. - uses: actions/setup-node@v6 with: - node-version: 22 + node-version: 24 + check-latest: true cache: npm registry-url: "https://registry.npmjs.org" - # Trusted publishing allows only `npm stage publish`, which needs npm >= 11.15.0. - - run: npm install -g npm@11 # tsc and npm publish load no native addon. - run: npm ci --ignore-scripts - run: npm run build