Lerna version without GIT tags in microservice monorepo #804
-
|
Hi, In fact, my project (nestJS) is set up as a monorepo and consists of :
When I execute the "version" command, lerna creates a tag for each of the microservices that have changed and undergone a version bump. But I don't really want to clutter my repo with an huge number of tags. How does the "version" command detect changes in packages ? Ideally, what I would like is that for a release:
Can this be achieved in some way with lerna ? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
I'm not sure if you're using conventional changelog or not but you probably should since it will probably help with some of these questions. Personally I only ever used conventional changelog with a fixed version for all package, the version is calculated by I would suggest you look at the original Lerna issues and/or ask questions on Stack Overflow which is probably the best thing to do in this case. Lerna-Lite is just a repackaged Lerna (except that the newer Lerna is becoming another Nx product and Lerna-Lite is not).
We never include the root level package in the release, the only thing that can be updated is the root changelog (requires conventional changelog) but that only happens when you're using fixed version (aka not Searching on Lerna's GitHub, I found this issue 2050 |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for this complete answer. I will take a look to conventional-changelog, see what I can do with. Thank you ! |
Beta Was this translation helpful? Give feedback.
-
|
ah yeah for sure, I'm just emphasizing fixed version because I have more experiences with it but indeed for your use case then |
Beta Was this translation helpful? Give feedback.
-
|
It's a short form for Kubernetes ;-) |
Beta Was this translation helpful? Give feedback.
I'm not sure if you're using conventional changelog or not but you probably should since it will probably help with some of these questions. Personally I only ever used conventional changelog with a fixed version for all package, the version is calculated by
conventional-changelog-recommend-bumpand Lerna only uses it to update the packages and changelogs. I don't have enough knowledge of Lerna and Git to answer your questions and the goal of this project was mainly created for maintenance and to make it smaller by making all commands as optional, however I don't have full knowledge of how everything works, I just maintain it like I said.I would suggest you look at the original Lerna iss…