[BUG] v 7.3.0 when publishing to private rep You need to authorize this machine using 'npm adduser'

[sysmat]

Current Behavior:

Can not publish(This command requires you to be logged in) but I adduser successfully

Expected Behavior:

• it work with npm v 6

Steps To Reproduce:

• npm adduser --registry=https://zelenjak.arnes.si/nexus/repository/ArnesNpm/
• ok login and in my .npmrc I get

registry=https://zelenjak.arnes.si/nexus/repository/ArnesGroupNPM/
//zelenjak.arnes.si/nexus/repository/ArnesNpm/:_authToken=NpmToken.XXXXXXXXX

• in my package I have:

,
  "publishConfig": {
    "registry": "https://zelenjak.arnes.si/nexus/repository/ArnesNpm/"
  },

• when running npm publish I got error:

npm ERR! code ENEEDAUTH
npm ERR! need auth This command requires you to be logged in.
npm ERR! need auth You need to authorize this machine using `npm adduser`

Environments:

• Node: 12.6.0
• npm: 7.3.0
• OS: win32 x64

[ljharb]

ArnesGroupNpm and ArnesNpm are different registries.

[sysmat]

This is nexus:

• ArnesGroupNpm is group repo(combining public and private) and it is for download
• ArnesNpm is private hosted repo and used for upload
• it works with npm 6
• publishConfig has ArnesNpm and _authToken in .npmrc is for ArnesNpm

[ljharb]

Ah, true - the publishConfig's registry is the one that's authed in npmrc.

[foxxyz]

Likely related to #2411. Try npm publish --registry <registry_url> as a workaround.

Fix underway in #2445.

[manuelottlik]

I am publishing my npm packages to my private npm registry via GitHub Actions and had the same issue.

Am I correct that this currently effects everyone that uses npm publish in CI to a private registry?

[foxxyz]

I am publishing my npm packages to my private npm registry via GitHub Actions and had the same issue.

Am I correct that this currently effects everyone that uses npm publish in CI to a private registry?

That's been my findings so far. I hope the CLI team fixes this quickly.