conventional prerelease not generating a prerelease version

Expected Behavior

one of these inputs:

lerna version --conventional-commits --conventional-prerelease
lerna version --conventional-commits --conventional-prerelease=@loggi/fake-package
lerna version --conventional-commits --conventional-prerelease=*

generating this output:

Changes:
 - @loggi/fake-package: 6.4.0 => 6.5.0-alpha.0

Current Behavior

always generating this output:

Changes:
 - @loggi/fake-package: 6.4.0 => 6.5.0

Possible Solution

• i’m using the cli wrong

lerna.json

{
  "version": "6.4.0",
  "changelog": {
    "repo": "loggi/fake-ui",
    "cacheDir": ".changelog",
    "labels": {
      "PR: Breaking Change :boom:": ":boom: Breaking Change",
      "PR: New Feature :rocket:": ":rocket: New Feature",
      "PR: Bug Fix :bug:": ":bug: Bug Fix",
      "PR: Polish :nail_care:": ":nail_care: Polish",
      "PR: Docs :memo:": ":memo: Documentation",
      "PR: Internal :house:": ":house: Internal"
    }
  },
  "packages": ["apps/*", "components/", "libs/*", "targets/*"]
}

Context

i’m trying to setup an automated prerelease setup (version & publish), but can’t get the version command right.

lerna version prerelease --conventional-commits --conventional-prerelease

worked, but bumped a patch instead of following conventional commits and bumping a minor. (committed using feat)

Your Environment

Executable	Version
lerna --version	3.13.1
npm --version	6.4.1
node --version	8.15.1

OS	Version
macOS Sierra	10.12.3

[evocateur]

lerna version --conventional-prerelease was released in v3.14.0. You report lerna --version as 3.13.1, so…

npm rm -D lerna
npm i -D lerna@latest

[github-actions[bot]]

Hi Folks 👋

You will have seen in our message above that we at Nrwl are working really hard to bring the lerna repo up to date with what matters most to its community in June 2022.

As previously stated in that message, because we have not heard from the original author of this issue within the last 14 days, we are now automatically closing it.

If any users, including the original author, are still impacted by this issue then we still want to hear from you!

All we ask is that you first update to the latest lerna (5.1.4 at the time of writing) to make sure it is still reproducible, and then fill out one of our new issue templates, providing all the requested details which apply to your situation:

https://github.com/lerna/lerna/issues/new/choose

Many thanks again! 🙏

---

P.S. Over and above getting to grips with the repo, we have also been hard at work launching a new website, resolving all vulnerabilities, merging exciting new features and reigniting community PR contributions! 🚀

You can read our recent blog post to learn more about what we’ve been up to: https://blog.nrwl.io/lerna-5-1-new-website-new-guides-new-lerna-example-repo-distributed-caching-support-and-speed-64d66410bec7