Repository navigation
Remove global npm install from publish workflow - #790
Merged
Merged
Conversation
Co-authored-by: Hugo-ter-Doest <7829083+Hugo-ter-Doest@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update GitHub Actions workflow to remove npm global install step
Remove global npm install from publish workflow
Oct 22, 2026
Hugo-ter-Doest
marked this pull request as ready for review
October 22, 2026 11:48
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.
A publish run failed with
MODULE_NOT_FOUNDforpromise-retryinside npm's own Arborist code, not in project code. This PR stops the workflow from replacing the runner's npm, so it uses the npm bundled withactions/setup-node..github/workflows/npm-publish.ymlpublish-npmsteprun: npm install --global npm@12.2.1.- uses: actions/setup-node@v4 with: node-version: 22.22.2 registry-url: https://registry.npmjs.org/ - - run: npm install --global npm@12.2.1 - run: npm ciReview notes
publish-npmstill pins Node22.22.2, the version the failed run used. If thepromise-retryerror comes back, the next step is probably pinning Node 20, as thebuildjob already does.npm stage publish. Please confirm the npm bundled with Node 22.22.2 supports it, since the removed step was the only thing installing a different npm.