Publish attempt without being logged in failed and can't re-publish

Lerna is fairly aggressive in thinking it’s published a package when it hasn’t.

I attempted a publish, it failed when I wasn’t logged in to npm.

Lerna now believes it’s published because the packages are version bumped locally, there are no new commits and that’s it.

I’m now having to figure out the --force-publish flag, which I struggle to get working with zsh:"

$ lerna publish --force-publish=*
zsh: no matches found: --force-publish=*

$ lerna publish --force-publish="*"                                                  1 ↵
info cli using local version of lerna
lerna notice cli v3.10.7
lerna info current version 0.0.6
lerna info Looking for changed packages since v0.0.6
lerna WARN force-publish all packages
lerna ERR! ERELEASED The current commit has already been released. Please make new commitsbefore continuing.

[gauntface]

Would it be possible for lerna to verify npm auth before versioning?

[evocateur]

Clearly I’m not doing a good enough job of documenting the existing options for lerna publish, because there have been positional arguments available for several months now to help in just the sort of situation you’re describing here.

You don’t need --force-publish if you’re on the commit generated by lerna version. lerna publish from-git is all you need in that context.