Skip to content

ci: require canonical npm token for publishing#120

Merged
cbusillo merged 1 commit into
mainfrom
fix/npm-publish-canonical-token
May 24, 2026
Merged

ci: require canonical npm token for publishing#120
cbusillo merged 1 commit into
mainfrom
fix/npm-publish-canonical-token

Conversation

@cbusillo
Copy link
Copy Markdown
Owner

Summary

  • treat NPM_TOKEN as the only credential that enables npm publishing
  • avoid using ambient NODE_AUTH_TOKEN from self-hosted runners as publish evidence
  • keep GitHub Release publishing green when NPM_TOKEN is intentionally absent

Validation

@cbusillo cbusillo merged commit 1eae4b9 into main May 24, 2026
1 check passed
@cbusillo cbusillo deleted the fix/npm-publish-canonical-token branch May 24, 2026 11:51
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