no-git-push not working after 3.18.0
See original GitHub issue15: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 |
Issue Analytics
- State:
- Created 4 years ago
- Comments:16 (8 by maintainers)
Top Results From Across the Web
3.18.0 Hotfix 4 - Patch Notes
3.18.0 Hotfix 4. Fixed a bug where players were unable to teleport to another player's hideout while they were in a map.
Read more >[PoE 3.18] The Biggest Problem in PoE and How to Fix it
I go over the biggest problem in trade and why GGG's original trade design philosophy and manifesto is outdated. 0:00 - Intro and...
Read more >League Start is RUINED If this Bug Isn't Fixed - 3.18 Sentinel
League Start is RUINED If this Bug Isn't Fixed - 3.18 Sentinel ... Exile 3.18 Sentinel League | A fatal flaw in minions,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub 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.
I’m sorry my fuckups have caused you pain. Please stop berating me, now.