Skip to content

ci(publish): select npm by Node version #542

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

Closed
prd-carapulse wants to merge 1 commit into from
Closed

ci(publish): select npm by Node version #542

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
25 changes: 21 additions & 4 deletions .github/workflows/publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,10 +51,27 @@ jobs:
registry-url: https://registry.npmjs.org
scope: '@morpho-org'

# Trusted publishing requires npm >= 11.5.1, but Node 22.22.2's bundled npm 10.9.7
# currently fails to self-upgrade directly to npm@latest with MODULE_NOT_FOUND
# (missing promise-retry). Pin a known-good npm 11 release instead.
- run: npm install -g npm@11.11.0
- name: Select npm version for trusted publishing
id: npm-version
run: |
case "$(node -p "process.versions.node.split('.')[0]")" in
22)
echo 'version=11.11.1' >> "$GITHUB_OUTPUT"
;;
24)
echo 'version=latest' >> "$GITHUB_OUTPUT"
;;
*)
echo "Unsupported Node.js version for trusted publishing: $(node -v)" >&2
exit 1
;;
esac

# Trusted publishing requires npm >= 11.5.1.
# Node 22.22.2's bundled npm 10.9.7 currently fails to self-upgrade to npm 11.12.x
# with MODULE_NOT_FOUND (missing promise-retry), so keep Node 22 on the newest
# working npm (11.11.1). Node 24's bundled npm 11.11.0 can upgrade to npm@latest.
- run: npm install -g npm@${{ steps.npm-version.outputs.version }}

- run: pnpm install --frozen-lockfile

Expand Down
Loading