You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Expected Behavior
It should spot the changes the same way in either ways.
Steps to Reproduce
I got two packages ( pkg-a and pkg-b ), where pkg-b depends on pkg-a.
I published both of them with 10.3.0-ticket-1234-1 as version.
I apply some changes on pkg-b and commit it.
When I run npx lerna publish and then select the custom version option from the prompt, and input the next version as 10.3.0-ticket-1234-2, it identifies pkg-b as the only changed package, which is correct.
However, if I provide the version along with the command like npx lerna publish 10.3.0-ticket-1234-2, it cannot identify the changed packages correctly and wanna publish both pkg-a and pkg-b.
Current Behavior
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.Expected Behavior
It should spot the changes the same way in either ways.
Steps to Reproduce
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
.Failure Logs / Configuration
lerna.json
Environment
The text was updated successfully, but these errors were encountered: