CICDL-258: Test OIDC with id-token permission on consumer job#28
Merged
pipedrive-public-gha-bot[bot] merged 2 commits intoMay 20, 2026
Merged
Conversation
evenluiv
approved these changes
May 20, 2026
evenluiv
approved these changes
May 20, 2026
3 tasks
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.
Summary
Third test iteration for NPM Trusted Publishers (OIDC).
permissions: id-token: writeto the consumerpublishjob — this is required at every level of the reusable workflow chain; setting it only in the reusable workflow is not sufficientCICDL-258-use-trusted-providersbranchHow to trigger
Add the
npm-ready-for-publishlabel.Expected outcome
GITHUB_TOKEN Permissions in the run log should now show
id-token: write, and npm should authenticate via OIDC withoutENEEDAUTH.🤖 Generated with Claude Code