incompatible with pnpm monorepo

[NullVoxPopuli]

I recently converted a monorepo from yarn to pnpm, and now publishing won't happen.

4:36:23 PM] [semantic-release] [@semantic-release/npm] › ℹ  Verify authentication for registry https://registry.npmjs.org
[4:36:23 PM] [semantic-release] [@semantic-release/npm] › ℹ  Reading npm config from /home/nullvoxpopuli/.npmrc
npm ERR! code ENOWORKSPACES
npm ERR! This command does not support workspaces.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/nullvoxpopuli/.npm/_logs/2022-04-09T20_36_24_000Z-debug-0.log
[4:36:24 PM] [semantic-release] › ✖  Failed step "verifyConditions" of plugin "@semantic-release/npm"
[4:36:24 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/github"

[browniebroke]

I have the same error with npm workspaces. The traceback points at this line:

npm/lib/verify-auth.js

Line 21 in 4b33e5b

const whoamiResult = execa('npm', ['whoami', '--userconfig', npmrc, '--registry', registry], {

Also, I can reproduce locally by logging in, moving into one of the workspace of the monorepo and running: npm whoami

[browniebroke]

The command works fine with [email protected] but not with [email protected]

[browniebroke]

And it seems to be fixed in [email protected] (assume it was part of npm/cli#4479)

[manast]

I also have got this error, is there any workaround for this, can we just force the use of [email protected] on the plugin?

[hongaar]

Still have this problem with npm 8.19.2:

node@9a0111889c1a: /workspaces/mokr on main [$]
$ cat .npmrc 
workspaces = true

node@9a0111889c1a: /workspaces/mokr on main [$]
$ npm -v
8.19.2

node@9a0111889c1a: /workspaces/mokr on main [$]
$ npm whoami
npm ERR! code ENOWORKSPACES
npm ERR! This command does not support workspaces.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/node/.npm/_logs/2022-11-24T10_59_40_560Z-debug-0.log

Opened #529 to address this

[jedwards1211]

@NullVoxPopuli do you also have the workspaces = true npm config setting like @hongaar? If so you could work around by doing npm config set workspaces=false before running semantic-release, and the title isn't quite right because that setting isn't required for monorepos, it's just an option. I haven't run into this issue on my pnpm monorepos