Skip to content

Commit a300810

Browse files
committed
chore(release): work around actios/setup-node mal-interaction
actions/setup-node makes a default NODE_AUTH_TOKEN if none is set, which breaks OIDC It was the root cause of the publishing trauma as discovered when setting a real one in worked, after seeing the env contained a fake one. That led to discovery of this issue: actions/setup-node#1440
1 parent 748e89f commit a300810

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

.github/workflows/publish.yml

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,8 +56,9 @@ jobs:
5656
env:
5757
# No NPM token needed, all of the packages have been configured
5858
# on npmjs.com with this workflow file as an OIDC "Trusted Publisher"
59-
# However as of 20251208 we still need an NPM token as OIDC failing...
60-
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
59+
# You do have to clear it from the actions/setup-node default value though,
60+
# or publishing will fail, see: https://github.com/actions/setup-node/issues/1440
61+
NODE_AUTH_TOKEN: ""
6162
# org admin Github Token required for the changelog/tag commit+push
6263
# to work via an exception to branch protection rules
6364
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}

0 commit comments

Comments
 (0)