`lerna publish` unable to authenticate with Artifactory

We’re trying to run lerna publish in Jenkins. We’re using private Artifactory and configuring the auth via .npmrc file. lerna publish fails to authenticate successfully.

Expected Behavior

Using the same .npmrc file we’re able to successfully run yarn publish after building the packages separately, so we’d expect Lerna to be able to do the same.

• if Lerna requires different configuration in order to authenticate with private npm registries like Artifactory it would be useful for that to be documented
• if Lerna doesn’t support auth via the .npmrc file it would be nice for it to do so or to offer some alternative

Current Behavior

When running lerna publish we get:

...
14:29:46  lerna info publish Publishing packages to npm...
14:29:46  lerna notice Skipping all user and access validation due to third-party registry
14:29:46  lerna notice Make sure you're authenticated properly ¯\_(ツ)_/¯
14:29:48  lerna http fetch PUT 401 https://artifactory.???/api/npm/???/??? 2819ms
14:29:48  lerna ERR! E401 Unable to authenticate, need: Basic realm="Artifactory Realm"
14:29:48  error Command failed with exit code 1.

Possible Solution

• support auth via .npmrc file

Steps to Reproduce (for bugs)

.npmrc file looks like this:

@???:registry=https://artifactory.???.???.net/api/npm/???/
//artifactory.???.???.net/api/npm/???/:_password=${ARTIFACTORY_TOKEN}
//artifactory.???.???.net/api/npm/???/:username=???
//artifactory.???.???.net/api/npm/???/:email=???@???.com
//artifactory.???.???.net/api/npm/???/:always-auth=true

and we run the command lerna publish

lerna.json

{
  "packages": ["packages/*"],
  "version": "independent",
  "npmClient": "yarn",
  "useWorkspaces": true,
  "command": {
    "publish": {
      "conventionalCommits": true,
      "yes": true,
      "message": "chore(release): publish",
      "exact": true
    }
  }
}

Context

At the moment we’re doing a hacky workaround to publish our packages by running:

• lerna version to get the versions bumps required
• yarn lerna run to build the new packages
• publish with yarn publish

Overall it feels like we’re unable to use Lerna as it was intended

Your Environment

Running the build in Jenkins in a Debian stretch docker container

Executable	Version
lerna --version	v3.22.1
npm --version	6.14.5
yarn --version	1.22.4
node --version	v12.18.1

OS	Version
Debian	GNU/Linux 9 (stretch)

[wldcordeiro]

So is there a fix coming for v4.x? Don’t think it’s tenable to have people on prior major versions in the long term.

[saulske]

I had to downgrade to @3.22.0 in order to have it working. Other options did not help. 4.0.0 is not stable.