Doesn't work well with independent mode

[hzoo]

Example below

Since each thing is independent it doesn't make sense to have a changelog entry per release since each one is seperate.

---

Changelog for 2016-08-31

Bug Fix

• babel-preset-babili
  • #135 update older packages. (@hzoo)
  • #125 Revert "Throw upgrade error when babel version is less than 6.14.0". (@kangax)
  • #116 Throw upgrade error when babel version is less than 6.14.0. (@boopathi)
• babili
  • #128 add --no-babelrc option. (@hzoo)
• babel-plugin-minify-mangle-names, babel-preset-babili
  • #123 Add fix for other types of nodes in referencePaths. (@boopathi)
• babel-plugin-minify-simplify
  • #119 Fix bug - Conditionals transformation for impure paths. (@boopathi)

[Turbo87]

@hzoo should independent mode generate changelogs per project instead of a global one?

[hzoo]

I'm not sure anymore lol

[fahad19]

I feel it makes sense to generate changelogs per project (in independent mode).

[evocateur]

lerna publish --conventional-commits supports per-project changelogs in --independent mode, though admittedly not from lerna-changelog directly.

[sthzg]

@evocateur I also noticed that the --conventional-commits flag seems to work properly in independent mode.

though admittedly not from lerna-changelog directly

Not sure how to interpret this - was it meant as a hint to look into the code there and potentially reuse some of its logic to gather the relevant info or did you have some specific solution based on that in mind?

Update lerna version --conventional-commits seems to achieve the separate changelogs in 3.x, which obsoletes my question.

[zero-t4]

lerna publish --conventional-commits supports per-project changelogs in --independent mode, though admittedly not from lerna-changelog directly.

Why doesn't this flag mentioned in docs?

[kylemh]

I'd love to integrate some sort of fix for independent mode. I quite like the idea of label-driven changelogs vs. a commit message standard.

Where would this change need to be made?

I can clearly see where I can help infer the package names, but once I have them, I'm not sure how to run the changelog generator against each package. A backward compatible change would be to change repo to packages as an array of strings. A non-independent monorepo would simply be an array of one item.

Do we still want one root-level CHANGELOG.md or should it be per package?

If it's root-level, should there be any new formatting?

[kylemh]

@Turbo87 any comments on the above? Really interested in getting this working. I want the PR labels stuff so bad - think it's so much better than relying on commit linting.

[Turbo87]

unfortunately I don't use lerna or yarn workspaces so it's hard for me to comment on this 🙁