Closed sebastienfi closed 3 years ago
To find out how a major version breaks compat I usually look at the commit list:
You can see move to ES2016
in there and that's probably it.
The diff seems to confirm it, there are no changes to the readme so the API is the same: https://github.com/Qix-/color-convert/compare/1.9.3...master
@Qix- If you use np
to publish it will generate a changelog for you and open a new GitHub Releases draft ;)
Changelog isn't something I'm interested in, and I'm not a huge fan of automation tools like np
as I've had them bite me before (e.g. release
).
I will, however, begin to add summations to the Releases page upon pushing releases.
Looking at the breaking change information in your changelog because I wanted to migrate from 1.x to 2.x, and couldn't find any. I recommend using NPM Package
stanrdard-version
and start usingconventional-commits
.