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
I'm having some tests with Lerna to check if we can easily use it on our monorepo project (ionic frontend + nestJS backend as a main gateway and 17 independent microservices).
So far, everything seemed to be working as expected with conventional commits until I performed a major update test.
Since then, Version only suggests a major bump for all changed packages, even if the release only contains a 'fix' commit.
My Git logs :
Lerna version bump suggestion :
As we can see, I only committed a fix for the chatbot microservice since the last release (tag v2.0.0), but 'version' suggests a major bump for the impacted microservice (3.0.0 instead of 2.0.1)
Expected Behavior
Suggest a patch bump
Steps to Reproduce
Configure a mono repo project with npm workspaces
Configure lerna version with independent mode, noPush and noGitTagVersion
Do a commit with a breaking change
Execute lerna version
Check that version suggests a major update and confirm
Current Behavior
I'm having some tests with Lerna to check if we can easily use it on our monorepo project (ionic frontend + nestJS backend as a main gateway and 17 independent microservices).
So far, everything seemed to be working as expected with conventional commits until I performed a major update test.
Since then, Version only suggests a major bump for all changed packages, even if the release only contains a 'fix' commit.
My Git logs :
Lerna version bump suggestion :
As we can see, I only committed a fix for the chatbot microservice since the last release (tag v2.0.0), but 'version' suggests a major bump for the impacted microservice (3.0.0 instead of 2.0.1)
Expected Behavior
Suggest a patch bump
Steps to Reproduce
Configuration
lerna.json
project directory
main package.json
Environment
The text was updated successfully, but these errors were encountered: