Skip to content

fix: bump Node to 22 for npm trusted publishers support#7

Merged
sharanmoore merged 2 commits into
mainfrom
fix/publish-oidc
Jun 29, 2026
Merged

fix: bump Node to 22 for npm trusted publishers support#7
sharanmoore merged 2 commits into
mainfrom
fix/publish-oidc

Conversation

@sharanmoore

@sharanmoore sharanmoore commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

The publish workflow was failing because npm trusted publishers requires Node 22.14.0+ and npm 11.5.1+. We were running Node 20 (npm 10), which doesn't support the OIDC authentication flow.

Changes:

  • Node version: 20 → 22
  • Removed cache: npm — the npm trusted publishers docs explicitly recommend disabling package manager caching in release builds (# never use caching in release builds), though no further rationale is given; likely to ensure a clean, reproducible install from the registry
  • Removed --provenance flag — when publishing via trusted publishers from a public GitHub Actions workflow, npm generates provenance automatically without needing the flag

After merging, the existing v0.1.1 tag will need to be deleted and re-pushed to trigger a clean run.

@sharanmoore sharanmoore requested review from a team as code owners June 29, 2026 16:48
@sharanmoore sharanmoore requested review from gmtuca and nlathia June 29, 2026 16:54
@sharanmoore sharanmoore merged commit 545a230 into main Jun 29, 2026
2 checks passed
@sharanmoore sharanmoore deleted the fix/publish-oidc branch June 29, 2026 16:56
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