Skip to content

fix npm install #79

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
simongdavies merged 1 commit into from
Apr 23, 2026
+9 −1
Merged

fix npm install #79

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
10 changes: 9 additions & 1 deletion .github/workflows/publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -188,8 +188,16 @@ jobs:

# Trusted publishing requires npm >=11.5.1 for OIDC token exchange.
# Pin to ^11.5.1 so we don't silently get an older 11.x that lacks OIDC.
#
# Bootstrap via `npx` rather than `npm install -g npm@...` — the latter
# hits a long-standing npm self-upgrade bug (reproduces on github-hosted
# runners too) where mid-reify npm unlinks its own `promise-retry` dep
# and dies with MODULE_NOT_FOUND. Using a fresh npx-fetched npm to
# install itself globally sidesteps the half-upgraded state entirely.
- name: Upgrade npm for trusted publishing
run: npm install -g npm@^11.5.1 && npm --version
run: |
npx --yes npm@^11.5.1 install -g --force npm@^11.5.1
npm --version

- name: Download npm tarball
uses: actions/download-artifact@v8
Expand Down
Loading