New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot spot the changed packages correctly when a custom version provided as command parameter #845
Comments
I think that is the default behavior of Lerna and it was added by the original author of Lerna When providing a version, it's defined as a global version and I'm assuming it's for probably all packages (so I'm guessing it's falling under either line 438 or 441) and it seems to be using These are all just assumptions, you should troubleshoot it yourself. I saw you've opened the same ticket on Lerna's project, we'll see if they ever reply. lerna-lite/packages/version/src/version-command.ts Lines 437 to 470 in 291bf01
|
Describe the bug
Lerna cannot detect changed packages when publishing with a custom version, provided as
publish
command's parameter. But can figure out when providing the same custom version using prompt.Expectation
It should spot the changes the same way in either ways.
Reproduction
10.3.0-ticket-1234-1
as version.npx lerna publish
and then select thecustom version
option from the prompt, and input the next version as10.3.0-ticket-1234-2
, it identifies pkg-b as the only changed package, which is correct.npx lerna publish 10.3.0-ticket-1234-2
, it cannot identify the changed packages correctly and wanna publish bothpkg-a
andpkg-b
.Lerna config and logs
lerna.json
Environment Info
Used Package Manager
npm
Validations
The text was updated successfully, but these errors were encountered: