document lerna as monorepo option

[blackxored]

I've read a lot of threads without a conclusive answer. Is there monorepo support in standard-version or planned?

• Multiple changelog generator including a root changelog.
• Multiple package version bumps at once.
• etc

[stevemao]

lerna is already using conventional-changelog. I guess we should document it.

[bcoe]

@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.

[blackxored]

Yes, I found lerna's --conventional-commits eventually. However, I think this package has a couple of more options. Lerna won't still give me a combined changelog at the root, unfortunately.

[pantoninho]

What's the state of this issue?

I don't understand if I should use lerna's option to create a conventional-changelog or use this package instead.

[inakiarroyo]

@pantoninho I am using the one provided by lerna. At the moment with conventional-changelog/standard-version you can't have independent versions and generated CHANGELOG.md with the correct meta-info on them, because it bumps all the packages with the same version without respect the independent option.

For the first creation of the each CHANGELOG.md I use this independent changelog generation tip

And after it, having in your lerna.json file:

"command": {
    "version": {
       "message": "chore(release): publish",
       "conventionalCommits": true,
       "yes": true
    }
  }

you can simple call npx lerna version which will update your CHANGELOG.md files, will bump your package versions respecting them with the conventional commit preset chosen and will respect the independent versioning for each package.

[coder2000]

What if we are not using lerna? Is there still a way to use this with a monorepo?

[codeandcats]

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?

[snebjorn]

Did anyone make some progress on this?

[micaelmbagira]

@snebjorn @codeandcats @bcoe I have a MR opened https://github.com/conventional-changelog/standard-version/pull/503 which enables that

[devjayantmalik]

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?

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.

[phun-ky]

@micaelmbagira nice work on the PR, but how can we put together this with standard-version so we can drop lerna completely?

[ipleten]

How can I add docs, perf, test and other features to conventional changelog? They are currently just simply being ignored.