Update publishing to use trusted publisher flow#47
Closed
AaronAtDuo wants to merge 1 commit intomainfrom
Closed
Conversation
AaronAtDuo
commented
Nov 17, 2025
Comment on lines
36
to
37
| env: | ||
| NODE_AUTH_TOKEN: ${{secrets.npm_token}} |
Contributor
Author
There was a problem hiding this comment.
Suggested change
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
1 participant
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.
Description
Add OIDC write permission setup to the NPM publishing flow
Motivation and Context
To align with NPM's new security practices
How Has This Been Tested?
It has not yet been
Types of Changes