lerna: no-git-push not working after 3.18.0

15:41:24 $ lerna publish prerelease --canary --exact --yes --no-git-tag-version --no-git-push --no-git-reset --no-changelog --dist-tag=pr-157 --preid=alpha-52b7893
15:41:24 ERR! lerna Unknown arguments: git-push, gitPush
15:41:24 error Command failed with exit code 1.

Expected Behavior

Prior to 3.18.0, this does not error out, and publishes without pushing to git.

Current Behavior

Errors out as in above example

Steps to Reproduce (for bugs)

lerna.json

{
  "version": "independent",
  "npmClient": "yarn",
  "useWorkspaces": true,
  "conventionalCommits": true,
  "registry": <enterprise artifactory url>,
  "verifyAccess": false,
  "verifyRegistry": false,
}

Context

I’m currently unable to publish alphas without locking to a lower version of lerna.

Your Environment

Running on jenkins

Executable	Version
`lerna --version`	3.18.1
`npm --version`	6.10.1
`yarn --version`	1.15.2
`node --version`	8.9.0

OS	Version
NAME	VERSION

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 16 (8 by maintainers)

Most upvoted comments

@tkissing-work while I agree in principle clearly this was not @evocateur fault but an underlying package.

It’s not fair to put the blame on him. And even if you do feel there is responsibility, you should not be so rude.

Relax, I get the frustration, but let’s be civil. Let’s not make the person who runs a massive open source project almost by himself job harder than it needs to be.

mlavina on Oct 21, 2019

I’m sorry my fuckups have caused you pain. Please stop berating me, now.

evocateur on Oct 21, 2019

And SemVer doesn’t care if breaking my build now is “better” than silent errors, it only cares about compatibility. lerna 3.18.x is not compatible to 3.17.x. If lerna does not want to do SemVer, than at the very least you should put a warning into your readme and possibly switch to version numbers that do not suggest SemVer, so consumers know not to let renovate auto-update this dependency.

tkissing-work on Oct 21, 2019

@mlavina Yargs has been configured with .strict() for almost two years now. It appears Yargs 14 fixes some bugs that were previously obscuring it.

evocateur on Oct 21, 2019