release 2.0.0

[nwwells]

@lpinca, @3rd-Eden, @einaros... I don't have access on npm to publish this package, but I made some changes that will fix a few issues. Can you please release 1.2.0 or give me access to?

[lpinca]

@nwwells #34 is a breaking change so it must be a major (2.0.0).

[lpinca]

Let me know if you want to add more breaking changes like using ES6 features where possible before releasing 2.0.0 or you are good as is.

[nwwells]

How is it breaking? the command line API stays the same, no?

[lpinca]

ws@2 only works on Node.js 4.5.0 or greater.

…

Sent from my iPhone

On 21 Feb 2017, at 19:24, Nathan Wells ***@***.***> wrote: How is it breaking? the command line API stays the same, no? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or mute the thread.

[nwwells]

Ah. I'm down with a 2.0 upgrade then. I'll make the change and get back with you here soon

[nwwells]

fixed in c6dfcf8

[lpinca]

@nwwells ok I'll cut the release later or tomorrow. Please never bump the package.json version as we use a dedicated commit for the release like b682807.

[nwwells]

Understood.