Reason for changelog generation removal

[hishamanver]

Hey there, wrt the following in the readme --changelog was removed. Creating a changelog file is no longer supported.

is there any reason for this? We were really loving this capability.

[TomerFi]

Hi

Thank you for your feedback. There were multiple reasons for removing the changelog generation option.
This tool was used as a container image. Creating a file in a persistent volume requires read-write permissions, while read-only permissions are always a better approach. Also, tools like this usually work better when they do only one thing: it is easier to pipe and verify the output. Additionally, most tools used for releasing these days include a changelog generation option.

So, when I re-wrote this project as a Node.js package (instead of shell scripts), I figured if anyone needs this functionality, they can use the conventional-changelog-cli, which is the tool this image used behind the scenes.

But it should be simple to re-introduce to the project. I'll give it some thought and update this discussion.

[hishamanver]

Yeah that makes sense!

It was just a very convenient feature, I googled what i needed (versioning with changelog updates) and was pleasantly surprised by this project <3

To be honest, even simple stdout (as opposed to writes to file) would be sufficient - to avoid file permissions issues. Maybe controlled with a feature flag?

Regardless, happy to give https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-cli a go, seems to do what we are after from a changelog perspective, but will need containerisation.

Thanks for your consideration and suggestion :)

[TomerFi]

To be honest, even simple stdout (as opposed to writes to file) would be sufficient - to avoid file permissions issues. Maybe controlled with a feature flag?

Yes, that's exactly what I was thinking. I figured it should be pretty straightforward: if --changelog is true, then the stdout would be the changelog content. But when I tried it, I ran into something weird with one of the dependencies; it looked like a bug. But I had to drop it; I couldn't spare the time.