wish: Changelog

[markstos]

It would be helpful to have a human-friendly log of what's changed between versions. http://keepachangelog.com

[OverZealous]

I suppose, though I've only really made one breaking change so far. And this project is pretty well static at this point.

[markstos]

In my case, I'm running roughly 1.0 and was trying to figure out if upgrading to the latest version would fix the issue I was having. The Changelog would have been helpful. In this case it didn't take long to just test the new release by trying it out.

[OverZealous]

@nicolasalejandrorodriguez This was discussed in #90 and #89 and fixed in v2.0.0

Also, please don't comment on existing bugs with unrelated issues.

[OverZealous]

No problem, you don't have to delete your comment. Just make a new issue in the future. Thanks!

[jwhitmarsh]

Since this is open - why was the major version changed? Do we need to watch out for any breaking changes?

[OverZealous]

The library didn't specify a version for dependencies, leading to unexpected behavior as Chalk dropped support for old versions of Node. To prevent unexpected behavior, I released the update with specific version dependencies as a new major release.
For more details, please see #89

[markstos]

Releasing 2.0 would have been a great time to add the Changelog requested in this issue and could save further support time being spent to answer questions in the issue tracker about "why the major version bump?" since the answer is not easily found in a Changelog as expected.

[OverZealous]

I get that, it just wasn't a prioity since I was trying to get a fix out for people with broken builds, and was sick all last week.