Skip to content

ci(release): drop sudo so npm upgrade actually takes effect #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
milstan merged 1 commit into from
May 20, 2026
Merged

ci(release): drop sudo so npm upgrade actually takes effect #51

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,10 +119,15 @@ jobs:
working-directory: packages/mcp
run: |
set -euo pipefail
# Install npm@latest into the setup-node prefix (writable; no
# sudo). The runner image bundles npm 10.x with Node 22, but
# Trusted Publishers OIDC requires npm ≥ 11.5.1. Using `sudo`
# would install to /usr/local — outside setup-node's PATH —
# leaving the next `npm` call still pointing at 10.x.
# `--force` works around a MODULE_NOT_FOUND (promise-retry)
# error when npm upgrades itself in-place on the runner image.
sudo npm install -g npm@latest --force
npm --version
# error when npm upgrades itself in-place.
npm install -g npm@latest --force
echo "npm $(npm --version) at $(which npm)"
VERSION=$(node -p "require('./package.json').version")
# Idempotent: if @leadbay/mcp@$VERSION is already on npm, skip.
if npm view "@leadbay/mcp@$VERSION" version --silent 2>/dev/null; then
Expand Down
Loading