Switch to OIDC Trusted Publishers for npm publish#733
Open
Moser-ss wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
siirimangus
approved these changes
May 22, 2026
evenluiv
approved these changes
May 22, 2026
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
3 participants
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.
Switch npm publishing from token-based auth to OIDC Trusted Publishers.
use_trusted_publisher: trueto reusable workflow callpermissionsblock (id-token: write,contents: write) for OIDC token issuanceNPM_PUBLIC_PUBLISH_TOKENsecret needed after npmjs.org Trusted Publisher is configuredManual steps still required before E2E:
client-nodejsis in Pipedrive Public GHA Bot's repo access listPD_PUBLIC_GHA_BOT_CLIENT_IDvariable is availablepipedrivepackage (org:pipedrive, repo:client-nodejs, workflow:cicd_npm-publish.yml)