Getting 403s when publishing unpublished packages

I am experiencing an issue with publishing every so often. Sometimes lerna will tell me lerna ERR! E403 You cannot publish over the previously published versions even for version that aren’t published, or I had never published them before running the command.

• Example 1 - Publishing a canary for a PR 7.11.1-canary.619.8042.0. The 8042 is the build number, which would always be unique. Everything else published fine, and we always --force-publish. If you look on npm, this version was actually published when the command was run

• Example 2 - This was during an actual release. This one is a little different, the version it says was released never actually made it to npm

Expected Behavior

Should successfully publish previously unpublished version of package.

Current Behavior

Get an error for a version I have never released before.

Possible Solution

It feels like there may be an unawaited promise, or maybe npm is acting wonky?

Steps to Reproduce (for bugs)

See above linked examples. It’s only ever happened twice and it’s rare.

Context

This botched a few releases. Only 1 was an official release.

Your Environment

Executable	Version
lerna --version	3.17.0
npm --version	5.3.0
node --version	8.14

[hipstersmoothie]

A little more context to what the issue might be (this guy is an npm employee) https://twitter.com/mikemimik/status/1199762406735523840?s=21

On Thu, Nov 28, 2019 at 10:41 AM Wojtek Trocki [e-mail] wrote:

I think regression started after this update to all monorepos: aerogear/graphback#456 https://github.com/aerogear/graphback/pull/456

I will monitor situation as npm also were behaving strangely and post more info (Going to add verbose mode to release)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lerna/lerna/issues/2313?email_source=notifications&email_token=AAJDEBAUGG2PIAWUNC4QHW3QWAGGVA5CNFSM4JC7TKAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFNIT5Y#issuecomment-559581687, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJDEBEUWOETMTWZ3ESY2KTQWAGGVANCNFSM4JC7TKAA .

[wtrocki]

I think regression started after this update to all monorepos: https://github.com/aerogear/graphback/pull/456

I will monitor situation as npm also were behaving strangely and post more info (Going to add verbose mode to release)