Skip to content

fix: update Node to 20.x and upgrade npm for trusted publishing#455

Merged
shannah merged 1 commit intomasterfrom
claude/update-node-npm-oidc-c8y3e
Apr 12, 2026
Merged

fix: update Node to 20.x and upgrade npm for trusted publishing#455
shannah merged 1 commit intomasterfrom
claude/update-node-npm-oidc-c8y3e

Conversation

@shannah
Copy link
Copy Markdown
Owner

@shannah shannah commented Apr 12, 2026

Summary

  • Update actions/setup-node from v2 to v4 and Node from 16.x to 20.x in the GitHub Action (action.yml)
  • Add npm install -g npm@latest step after Node setup to ensure npm supports trusted publishing (OIDC provenance requires npm 9.5+)
  • Node 16 ships with npm 8.x which lacks trusted publishing support, breaking deploy_target: npm workflows that rely on OIDC provenance

This matches the pattern already used in jDeploy's own CI workflow (.github/workflows/maven.yml lines 33-38).

Test plan

  • Verify GitHub Action runs successfully with deploy_target: github
  • Verify GitHub Action runs successfully with deploy_target: npm using trusted publishing (OIDC)
  • Confirm npm version after upgrade step is 9.5+ (supporting --provenance)

https://claude.ai/code/session_013qz1NYPTSvpAWsjdDXZqLk

Node 16 ships with npm 8.x which doesn't support npm trusted publishing
(OIDC provenance), requiring npm 9.5+. This updates the GitHub Action to
use actions/setup-node@v4 with Node 20.x and adds an npm upgrade step,
matching the pattern already used in .github/workflows/maven.yml.

https://claude.ai/code/session_013qz1NYPTSvpAWsjdDXZqLk
@shannah shannah merged commit d2bf1b9 into master Apr 12, 2026
18 checks passed
@shannah shannah deleted the claude/update-node-npm-oidc-c8y3e branch April 12, 2026 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants