-
Notifications
You must be signed in to change notification settings - Fork 789
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
document lerna as monorepo option #225
Comments
lerna is already using |
@stevemao @blackxored; following up from @stevemao's comment. I helped add similar functionality to lerna, to the functionality in standard-version. I think we'd be smart to reference lerna in our README for standard-version. |
Yes, I found lerna's |
What's the state of this issue? I don't understand if I should use lerna's option to create a |
@pantoninho I am using the one provided by For the first creation of the each CHANGELOG.md I use this independent changelog generation tip And after it, having in your
you can simple call |
What if we are not using lerna? Is there still a way to use this with a monorepo? |
Yes, I'm curious how I can use standard-version in a mono-repo (configured using yarn workspaces, not lerna) consisting of multiple npm packages. Like is there a way to tell standard-version to only look at git commits that affected files under a certain path when building the change log and bumping the package version? |
Did anyone make some progress on this? |
@snebjorn @codeandcats @bcoe I have a MR opened #503 which enables that |
Is it possible now in 2021 to maintain monorepo with independent versions without lerna? Or do you have some plans for it? If above comment is possible, then what would be the steps to implement it, a example would be appreciated. |
@micaelmbagira nice work on the PR, but how can we put together this with |
How can I add docs, perf, test and other features to conventional changelog? They are currently just simply being ignored. |
I've read a lot of threads without a conclusive answer. Is there monorepo support in standard-version or planned?
The text was updated successfully, but these errors were encountered: