Open thombruce opened 1 month ago
Should packages have individual CHANGELOG's? Or should the monorepo maintain just one?
I'm gonna google to see if there's any conventional wisdom on that. My hunch would be... it makes more sense to maintain separate, per-package logs.
Okay, I'm coming up short on conventional wisdom... Instead I'm finding a bunch of different tools for managing monorepo changelogs, including some lerna specific ones.
Notable mentions:
Let's take a look at those and other options. I would LOVE for the changelog to be handled automatically (or based on a specific command / developer behaviour). I don't mind if this means rethinking commit messages or how we handle PRs. In fact, the more guidance and structure there, the better; mine are always a bit freeform.
Suggest we go with lerna-changelog and establish Conventional Commits as our commit messaging strat. See here for how the two apparently work together: https://medium.com/@askjkrishna/scaffolding-a-project-using-lerna-and-lerna-changelog-cad6156f6f36
Conventional Commits: https://www.conventionalcommits.org/en/v1.0.0/
Keep a CHANGELOG