missing release notes and tag for v3.0.0

[thecotne]

No description provided.

[AlexSwensen]

As seen here: 5ebe57f

I feel npm releases need to reflect releases in github, and should be shown as v3 with node 4+ as a dependency. Many developers (including myself) rely on this as part of our normal upgrade process. @nickmerwin

[Demven]

I was very confused by the absence of GitHub tag/release for v3.0.0. I need the changelog!

[martindale]

No release on GitHub... what are the changes in 3.0.0?

[ntwb]

I dug through the commit history to find the version I'm upgrading from 2.13.1

Grabbing that commit hash b9032a1 along with the 3.0.0 commit 2ed4d09 lets me compare changes since the first commit to the 3.0.0 commit: b9032a1...2ed4d09

I hope that helps others here, but yes, tagging at a minimum on GitHub would be appreciated, a changelog would be ice cream 🍨 http://keepachangelog.com/

[dijonkitchen]

This might be helpful too for changelog generation: https://github.com/conventional-changelog/conventional-changelog

[gertsonderby]

v3.0.2, same problem.

Maybe automate this some, as has been suggested?

[nickmerwin]

Thanks @gertsonderby and @thecotne, I've added release notes for v3.0.2.