Skip to content

ci: use npm Trusted Publishing instead of NPM_TOKEN - #24

Merged
TheStreamCode merged 1 commit into
mainfrom
chore/trusted-publishing
Oct 14, 2026
Merged

TheStreamCode merged 1 commit into
mainfrom
chore/trusted-publishing

Conversation

@TheStreamCode

Copy link
Copy Markdown
Owner

Summary

Switch the npm publish workflow to Trusted Publishing (OIDC): drop NODE_AUTH_TOKEN so npm authenticates the run from the id-token permission. Token auth fails with EOTP since classic tokens can no longer publish.

Changes

  • .github/workflows/publish.yml: removed NODE_AUTH_TOKEN env + bootstrap comment

Testing

  • CI matrix below (workflow file only; publish itself verified by re-running the v2.0.0 release afterwards)

Checklist

  • PR is focused on a single concern
  • README.md updated if user-facing behavior changed (N/A)
  • No API keys or credentials in code or examples
  • New provider entries document the base URL, model behavior, and authentication requirements (N/A)
  • Credential environment names are registered and tested when authentication is required (N/A)

Notes

  • Requires the Trusted Publisher already configured on npmjs.com for this repo + workflow.

@TheStreamCode
TheStreamCode merged commit b1c0925 into main Oct 14, 2026
9 checks passed
@TheStreamCode
TheStreamCode deleted the chore/trusted-publishing branch October 14, 2026 19:25
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