Lerna 3.0.0-rc.0 to 3.0.0 caused breaking changes with split of lerna version from publish

[kirbdee]

Expected Behavior

lerna publish to accept version flags prior to handle version bumping publishing

Current Behavior

have to explicitly call lerna version prior

Possible Solution

This should have been considered a breaking change.

Steps to Reproduce (for bugs)

lerna publish --skip-npm --conventional-commits --yes
Conventional was no longer being used

lerna.json

<!-- Please paste your `lerna.json` here -->

lerna-debug.log

<!-- If you have a `lerna-debug.log` available, please paste it here -->
<!-- Otherwise, feel free to delete this <details> block -->

Context

Your Environment

Executable	Version
lerna --version	VERSION
npm --version	VERSION
yarn --version	VERSION
node --version	VERSION

OS	Version
NAME	VERSION

[evocateur]

lerna version --conventional-commits --yes should work fine, is the error message not clear enough?

[kirbdee]

No that makes sense, I didn't notice it until I saw my CICD do something unexpected.

[evocateur]

That being said, we have integration tests that validate passing --conventional-commits to lerna publish passes it through successfully. I'll need a reproduction of your case to verify if it's an actual bug.

[kirbdee]

No worries, I've moved to 3.0.1 from the 3.0.0-rc.0 with the appropriate changes.

[evocateur]

I just realized I forgot to add a hidden --skip-npm yargs option to lerna publish, so this would indeed fail despite the internal aliasing already in place. Silly unit tests lying to me...

[lock]

This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.