Usage in monorepo nx workspace

Hi, I am using nx workspace to handle multiple angular projects as well as shared libraries. Let’ s assume a folder structure like this:

|_package.json
|_CHANGELOG.md
|_projectA
  |_package.json
  |__CHANGELOG.md
|_projectB
  |_package.json
  |_CHANGELOG.md

I am trying to figure out a way to use conventional-changelog in my release process. I want to have seperated changelogs for each project and one root changelog. By using conventional commits I would like to somehow define the scope of the commit (e.g. that this feat() only affects projectA and thus, is only mentioned in this specific changelog.

Is this possible or is this a wrong approach in a monorepo?

Help appreciated.

[snebjorn]

@sidyes I think I’ve found a solution. It’s not ideal, but it’ll do for now.

You put an .versionrc file in each sub folder with the "path": "." config. Then you run standard-version from each sub folder you want to update the changelog for.

Example https://github.com/snebjorn/akita/blob/refactor/nx-workspace/libs/akita-ng-entity-service/

[snebjorn]

I believe so. My initial test worked. But haven’t used it in the wild yet. But wait. There’s more! 🎈 🎉

I managed to improve upon it quite a bit. This combo makes it work from the repo root and without standard-version globally installed!

files in project folder: .yarnrc .versionrc

npm script in root: “release:akita-entity-service”: “yarn --cwd libs/akita-entity-service run standard-version”