How to use lerna with Github PRs and conventional commits? #3508
Unanswered
alethenorio
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am new to lerna but have been using conventional commits for a while now and I seem to fail to understand how lerna is meant to be used.
The flow I generally follow from commit to release is the following in my projects:
Through my research, I see that semantic release plugins for lerna for doing tagging and publishing are a bit of hit and miss where most are either no longer maintained or are in early days.
Since I have a project which is developed using lerna i thought I'd look to see how to emulate something like the flow described above using lerna.
After some reading I have landed on trying a combination of
version
andpublish
commands but I have run into some issues:version
wants to change files in the repository (for examplepackage.json
) and create a new commit. On top of that it wants to tag that commit which will only exist in the branch. I have not found a workflow that would allow for a smooth development experience with this command.publish
- by making use of the semantic release cli to create just the tag, I have tried to then usinglerna publish
to publish the applications in my repo however even usinglerna publish from-git
lerna seems to want to use the version in the package.json to publish and not the git tag associated with that commit.I am flexible on adapting the workflow to how lerna wants things to be done but there are a few things which I don't see being able to change
Rebase and Merge
in my PRs.How have people been using lerna with similar setups? Am I missing something in the above?
Beta Was this translation helpful? Give feedback.
All reactions