Publish not working for internal Artifactory registry

[brad-mccormick]

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 publish command 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:

No changesets found, attempting to publish any unpublished packages to npm
Found existing user .npmrc file
Didn't find existing auth token for the npm registry in the user .npmrc file, creating one
/home/runner/setup-pnpm/node_modules/.bin/pnpm run changeset:release 

[MikelArnaiz]

Provide an example of your .npmrc file

[uiolee]

same issue

[uiolee]

action/src/index.ts

Line 64 in 2bb9bcb

return /^\s*\/\/registry\.npmjs\.org\/:[_-]authToken=/i.test(line);

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

[nikparo]

I 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 a publish script in package.json, which I tried running in the changeset action as pnpm publish. The problem is that publish is a built in command, so to run the script you would need pnpm 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 }}

[vsnig]

I found a workaround, see this
They set the registry in the script
And authenticate in the workflow
Just tried and it worked