Skip to content

ci: use trusted publishing for npm release#27

Merged
sarveshsea merged 1 commit into
mainfrom
release/npm-trusted-publish
May 14, 2026
Merged

ci: use trusted publishing for npm release#27
sarveshsea merged 1 commit into
mainfrom
release/npm-trusted-publish

Conversation

@sarveshsea
Copy link
Copy Markdown
Owner

Summary

  • Moves the npm publish workflow to current trusted-publishing/OIDC defaults.
  • Uses Node 24/npm 11+ for npm trusted publishing support.
  • Keeps optional NPM_TOKEN fallback, but publishes without long-lived tokens when trusted publishing is configured.
  • Uses npm ci instead of rewriting the lockfile during release.

Verification

  • ruby YAML parse for .github/workflows/publish.yml passed.
  • Prior 1.0.2 package gates passed before the publish auth failure.

@sarveshsea sarveshsea merged commit fd2b756 into main May 14, 2026
2 checks passed
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.

1 participant