Npm user token fails on organization level runner #145332
Replies: 1 comment
-
We noticed the problem only happens in node 20.11.0. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Question
Body
Hi, we face a problem that the workflow to publish npm package to github package registry using self hosted runner.
When we run the workflow on a mac runner which added in the repo, it works fine. But when we run the workflow on other linux runners set in the organization doesn't work.
When checking with
npm whoami --registry=https://npm.pkg.github.com/
, on the mac runner added in the repo returnsgithub-actions[bot]
, which is expected. With that, all thenpm install
andnpm publish
in workflow works fine.But when we check on the linux runners added in organization level, same workflow with checking
npm whoami --registry=https://npm.pkg.github.com/
returns errorIn detailed npm log doesn't find further useful info
Together with that, the
npm publish
also got this 400 error.Is there any difference or extra configuration on Organization-Level runners need to do so the token for github package npm registry works fine? Or is that related to Linux? Or any other reasons?
Thanks a lot!
Beta Was this translation helpful? Give feedback.
All reactions