Repository navigation
ci(publish): npm >= 11.5.1 for trusted publishing (OIDC) - #190
Merged
Merged
Conversation
With the package's Trusted Publisher pointed at this repo's publish.yml on npmjs.com, npm exchanges the job's id-token for a one-off publish credential, so publishing stops depending on a long-lived NPM_TOKEN (npm is restricting 2FA-bypass tokens). NODE_AUTH_TOKEN stays as the fallback until every package is switched.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before
npm publish, npm is upgraded to >= 11.5.1. Once this package has a Trusted Publisher configured on npmjs.com (repo BlockRunAI/blockrun-mcp, workflow publish.yml), publishing goes through OIDC and no long-lived NPM_TOKEN is needed. NODE_AUTH_TOKEN stays as a fallback for now, so this is safe to merge before the npm side is configured. Merging does not publish a new version.