Repository navigation
Publish not working for internal Artifactory registry #336
Description
Activity
Provide an example of your .npmrc file
same issue
Line 64 in 2bb9bcb
Didn't find existing auth token for the npm registry in the user .npmrc file, creating one
the code just check npmjs token, which is the problem
Reacted by Irfan Maulana and oreptReacted by Irfan Maulana and oreptI got a similar error in a monorepo using pnpm (
You need to authorize this machine using npm adduser), and in my case it was because I had defined apublishscript inpackage.json, which I tried running in the changeset action aspnpm publish. The problem is thatpublishis a built in command, so to run the script you would needpnpm run publish. I opted to rename the script instead.package.json:{ "scripts": { - "publish": "pnpm build && pnpm changeset publish", + "publish-changeset": "pnpm build && pnpm changeset publish", } }.github/workflows/release.yaml:- name: "Create Release Pull Request or Publish to GCP" id: changesets uses: changesets/action@v1 with: - publish: pnpm publish + publish: pnpm publish-changeset env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
In my GitHub Workflow I'm creating a .npmrc with connection info for our internal Artifactory registry and then executing the changesets action. It fails on running the
pnpm changesets publishcommand with an "incorrect or missing password" and to run npm login. The documentation states that in the presence of a .npmrc, that user defined registry info is used instead. So why does it seem that its failing to use it and expecting an NPM_TOKEN? Here's an excerpt from the failed workflow: