ci(release): drop sudo so npm upgrade actually takes effect#51
Merged
Conversation
Previous PR ran `sudo npm install -g npm@latest` which installs to /usr/local/lib/node_modules — outside setup-node's bin prefix. The next `npm` call kept resolving to the runner-bundled npm 10.9.7 (visible in the failed run's `npm --version` output), which doesn't speak Trusted Publishers OIDC. Result: publish attempted token-style auth with no token, got 404. Without sudo, the install goes into setup-node's writable prefix (/opt/hostedtoolcache/node/.../bin/), so `npm --version` reflects the upgrade and OIDC kicks in. Also: echo `npm $(npm --version) at $(which npm)` for next-time debuggability. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Last OIDC attempt published with npm 10.9.7 (logged by the new
npm --versionline). sudo installs go outside setup-node's PATH; dropping sudo so the upgrade hits the active prefix and the nextnpm publishruns on npm ≥11.5.1 with OIDC support.