Versioning #8
Description
Hey there,
thanks for your work.
I wanted to quickly make a suggestion to keep a CHANGELOG.md as other projects do, tag your releases, use github releases or any similar kind of conveying, what your versions are.
Additional it would help if there would be notes on the releases. I have a old 1.x version here and see that the new version is 3.x.
I now am stuck either updating and 'trusting' that my way of using the library is not broken in v3 or I dig through all the code and guess which version of the code is actually published on NPM.
I understand that this is addtional work, but afaik there are some ways of automating that process:
- https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
- https://github.com/cookpete/auto-changelog
Just what a quick search came up with. I have only used GitHub for automatic generation of release notes yet.
Keep up the great work :)