From 21716eca1472177e9ad55bff5697a88d1c471941 Mon Sep 17 00:00:00 2001 From: Jairo Panduro Date: Tue, 14 Jul 2026 10:50:18 +0200 Subject: [PATCH] fix(ci): remove npm@latest upgrade in release workflow The release workflow ran `npm i -g npm@latest` before installing dependencies, silently picking up whatever npm CLI version was newest each run. A recent npm release added a new default restriction (EALLOWGIT) blocking git-protocol dependencies, breaking `npm i` for this repo's semantic-release-github-pullrequest devDependency (a git fork reference) and blocking every release since (including the 6.6.2 dependency bump in #433). No engines.npm pin here, so just drop the forced upgrade and let actions/setup-node's bundled npm run the install. --- .github/workflows/release.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 9df4504f..19802d12 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -20,7 +20,6 @@ jobs: - uses: actions/setup-node@v5 with: node-version: '22.x' - - run: npm i -g npm@latest - run: npm i - name: Check Git Commit name run: git log -1 --pretty=format:"%s" | npx commitlint