Documentation of releases/changes
ExplicitlyImplicit opened this issue · comments
This is just a tip from someone who uses your package in a production environment.
It would be great if you could document at least breaking changes when making new releases or follow semver. Latest minor update we had to figure out what was changed as we got error from your package (breaking change introduced by #29).
We totally understand that this might not be of prio for the scope of this package but just letting you know in case it is of use.
Keep up the great work!
Thanks @ExplicitlyImplicit, sorry for the inconveniences!