Actual changelog?

[jescalan]

So, v1.0 recently came out, and all that's in the changelog is two issues that were invalid and closed by the person that opened them. With semver, a major version boost indicates breaking changes. However, I can't really tell from the changelog if there were any changes at all.

Is there any chance you could update the changelog such that it reflects the changes between the versions? I just need to know if anything is breaking here, or what the differences are before I push this update out to my users.

Also, THANK YOU for your great work on this package, you are the best ✨

[madeleineostoja]

Yeah sorry about that, I've been meaning to add a big warning note in the README that the changelog is only autogenerated at the moment - figured it was better than nothing and I'm pretty flat out atm.

The main breaking changes to 1.0 were dropping support for Node 0.12 (4+ supported) and moving to PostCSS 6 (0.9 was on 5). I'm fairly certain that's all, but I'll have to go through the plugins to make sure nothing else changed, and update the changelog properly.

FYI there's another few breaking changes brewing in master for a 2.0, namely dropping postcss-alias, and if I get around to it passing config objects rather than booleans to plugins on init. Not sure when that will ship.