CHANGELOG

[bh-e]

It will be nice if you include a changelog

[kritik]

Yes, but I don't see any practical usage of it

[bh-e]

😄 . Its helpful for other users to track your changes in release .

[dbackeus]

Maybe time to implement a Changelog?

It's very rare to see gems without one these days and it's very helpful when using tools like dependabot to automate PR creation for dependencies which adds changelog info to the PR description.

[xtagon]

Yes, but I don't see any practical usage of it

When it's time to update dependencies, it's much easier to check a changelog to see what breaking changes were introduced, which versions of Ruby (or Rails or other frameworks) have new support or dropped support for old versions, and to see a summary of new features. Often when updating dependencies for a large application, many of the gems will have different compatibility than others.

Without a changelog, the only way to know is to check the entire commit log and figure it out from changesets and commit messages, which is much less practical IMO.

This is a good format to follow for consistency with other projects:

https://keepachangelog.com/en/1.0.0/