Changelog

[dionysiusmarquis]

Is your feature request related to a problem? Please describe.
I‘m currently using semantic-release together with semantic-release-monorepo.

I‘m already trying to only use the determined version and running all related ci tasks outside of semantic-release. But I wish I could replace all nodejs dependencies in this monorepo pipeline. This package is the first one I found that natively supports monorepos. The only thing missing would be changelogs.

Describe the solution you'd like
Providing monotepo project specific changelogs alongside the version output.

Describe alternatives you've considered
semantic-release -> nodejs dependency for all pipelines

go-semantic-release -> no monorepo support

Additional context
I know you want to keep it simple, but changelogs are the only missing thing for trying to this package for me.

[s0ders]

Generating changelog was something I often considered adding as a feature while developping this program.

The thing is, I didn't want this tool to become something like semantic-release which does a bunch of CI tasks and have you disable several modules when you simply want a SemVer. This tool is supposed to be one link in your CI pipeline that you can chain with other tools.

My point is: I'm pretty sure you can find a program that generates changelog for monorepo (such as this one which seems to do the job very well: https://github.com/changesets/changesets) and then chain it which go-semver-release after to get your next SemVer number.

[dionysiusmarquis]

Afaik changesets is primary a manual process. My goal is a generated changelog based on monorepo filtered commits since the last release.

I find the current semantic release options to complex myself, but for my use case the minimum is a semantic version and a changelog based on the corresponding commits, nothing more.

I took a look into the sourcecode, the paraser seems to already holding filtered commits. If I find the time I may try to fork and try to implement it.

[s0ders]

Indeed the parser already holds the necessary information to generate a changelog. I'm not firmly against this feature as long as it's fully optional and that it can be enabled with a toggle (e.g., flag, env. var., etc.).

Will try to look into this when I have some time, in the meantime if you want to fork this repo and make a PR, I'll gladdly review it!