Remove NODE_AUTH_TOKEN from npm publish step#43
Conversation
Removed NODE_AUTH_TOKEN from npm publish step.
Added permissions for id-token and contents in npmPublish workflow.
roryabraham
left a comment
There was a problem hiding this comment.
I think this workflow is used in a few places. It seems likely that just removing the NODE_AUTH_TOKEN will break all the places where this is used, right?
|
hmmm ok no I see... catching up on the required reading in https://docs.npmjs.com/trusted-publishers. Trying to get into npm settings so I can buddy-check them |
|
hrmm ok I see:
Given that, setting these permissions in this callable is probably redundant. |
roryabraham
left a comment
There was a problem hiding this comment.
@AndrewGable and I chatted, here's our gameplan:
- @AndrewGable will set up OIDC on all the npmjs packages on npmjs.org
- We will merge https://github.com/Expensify/GitHub-Actions/pull/43/files and Expensify/react-native-qrcode-svg#247, just to confirm that we do in fact need permissions in all repos
- If we do confirm this, then @AndrewGable will add permissions to all the repos and remove the permissions from GitHub-Actions
Details
Removed NODE_AUTH_TOKEN from npm publish step since we will now use ODIC method to publish npm libraries.
Related Issues
Related https://github.com/Expensify/Expensify/issues/558148