No Changelog so unable to asess changes between 2.0 and 3.0 without reading the code

[jberends]

Please describe a changelog in each release as people rely on it in production. When makeing a major version bump we always do a check what has been changed.

• either commit a CHANGELOG.md
• either put a changelog in the release message
• either put a changelog in the README.md

[vstoykov]

Yep it is a good idea to have one. If you have the time to do it, I'll be happy to merge it. For guidance you can use the git history: 2.0...3.0