From a9cc768b22c47d08d10891952cf1b51546073ed3 Mon Sep 17 00:00:00 2001 From: Jairo Panduro Date: Mon, 13 Jul 2026 17:34:14 +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. Nothing here requires a specific npm version (no engines.npm pin, lockfileVersion 3 works with any npm >=7), 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 0ed1bb9..1aa11fd 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