Provide changelog ?

[popod]

Hi, could you please provide changelog ?

A list of changes for each releases ?

Thank you

[Trott]

@simov If you want to automate releases with semantic-release, we can set up release-notes-generator to create a change log automatically. This is what I use for all my modules. The resulting change log files won't win any awards, but they are sufficient and they don't require any extra effort other than making sure we use conventional commits.

If that sounds like a good idea, I can do the configuration, but you'll need to add an npm publishing token as a GitHub secret to this repo (or I can do that if you give me admin access to the repo).

[simov]

@Trott sounds good. However, can we generate the changelog manually before every release and continue relying on us to provide the correct semver and to publish the module? I don't think GitHub supports that level of access for collaborators on personal repos, and I'm just thinking of a quick way to get that changelog generated.

[coreyward]

Bump on this. When I see something like this in my yarn outdated output, the first thing I do is go look for either Github Releases documenting the changes or a CHANGELOG file so I know whether or not there are breaking changes. I use slugify in libraries for other people, so out of respect for their time, I have to understand the impact before upgrading.

[simov]

@coreyward have a look at this https://github.com/simov/slugify/blob/9c7bc4bced93905982b7eae959887c8c4a626443/CHANGELOG.md

[coreyward]

@simov Heck yeah, super helpful. Can you merge that into main/master?

[simov]

Here it is https://github.com/simov/slugify/blob/master/CHANGELOG.md