Skip to content

fix(cicd): pin publish npm upgrade to npm@11, not @latest #92

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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
uladkasach merged 1 commit into from
Jul 28, 2026
Merged

fix(cicd): pin publish npm upgrade to npm@11, not @latest #92

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
6 changes: 5 additions & 1 deletion .github/workflows/.publish-npm.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,11 @@ jobs:
MIN_VERSION="11.5.1"
if [ "$(printf '%s\n' "$MIN_VERSION" "$NPM_VERSION" | sort -V | head -n1)" != "$MIN_VERSION" ]; then
echo "npm $NPM_VERSION < $MIN_VERSION, will upgrade npm now to support oidc..."
npm install -g npm@latest
# pin to npm@11 (not @latest): npm@12 requires node >=22.22.2, but this runner
# pins node via .nvmrc (v22.21.0); npm@11 satisfies the >=11.5.1 oidc minimum
# and supports the pinned node, so the upgrade cannot drift the engine out from
# under us again.
npm install -g npm@11
else
echo "npm $NPM_VERSION >= $MIN_VERSION, ready to use!"
fi
Expand Down
Loading