Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

publish with canary makes weird version.

See original GitHub issue

Expected Behavior

My current version is 0.5.0. and I pre-released the next tags by running below.

 lerna publish --canary --preid next --pre-dist-tag next --yes

Current Behavior

This command made new canary version successfully. But created version is different with what is expect. I expect it generate 0.5.0-next.0. But It generated 0.0.39-next.1.

I cannot understand where 0.0.39 come from… Is it bug? or is there my mistake?

lerna.json

{
  "packages": [
    "packages/*"
  ],
  "version": "independent",
  "npmClient": "yarn",
  "useWorkspaces": true,
  "command": {
    "publish": {
      "conventionalCommits": true
    }
  }
}

Your Environment

Executable	Version
`lerna --version`	3.22.1
`yarn --version`	1.22.10
`node --version`	12.18

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:5

Top GitHub Comments

1reaction

ChiefORZcommented, Jan 5, 2021

duplicate of #2622 and we fixed is with following changes in our forked lerna: #2572

@ChiefORZ This Fix is not released, right?

@reallifeliver no, unfortunately not - but we needed it desperately and thats why we packaged it on our own in our private registry…

ps: working since i opened the pull request, but had no more time to reason about and explain things unfortunately

0reactions

github-actions[bot]commented, Jun 17, 2022

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