-
Notifications
You must be signed in to change notification settings - Fork 763
Description
Affected Packages
pkg:@changesets/cli
Problem
While using this awesome project, I felt the desire to have a way to generate a global changelog / release. The idea is to have a single changelog, where each "release" could be identified by the versioning date (or something like that). To get an idea, the Blueprint.js changelog is an example of what I'm talking about (implemented with lerna).
I think the problem arises in my situation since all the packages I'm publishing are meant to be relevant. There are other projects (like pnpm, @changesets itself) where only the main package is relevant (like pnpm, @changesets/cli).
Proposed solution
I've already seen you're suggesting to implement a custom version command, relying on getReleasePlan and assembleReleasePlan. I'm pretty sure it is doable with a custom implementation, however I'd like to get feedback from you and maybe other folks using the project in order to know if feature could be relevant.
Furthermore, I'm not sure about your plans about custom changelog generation, is still the custom version command the preferred way to do this at the moment? I've seen the cli command implementation and it seems a bit complicated to implement it without basically reinventing the wheel. Even some suggestion here would be greatly appreciated!