Borked libuv 1.4.2 update

[19h]

Hey,

having trouble with libuv shipping alongside iojs.

I expected b2a0d8f to land libuv/libuv@252f362 which resides in libuv since March 18 (https://github.com/libuv/libuv/blob/v1.x/include/uv.h#L646-L654).

But then I noticed that 1.4.2 was tagged way before the landing (February 25). That is, could you please both tag libuv 1.4.3 and land it?

Relevant cross-issue: FrontierPsychiatrist/node-spotify#93 (comment)

cc @indutny @saghul

[indutny]

@saghul: we need a release to update it ;)

[saghul]

I plan to release libuv 1.5.0 tonight / tomorrow morning.

[Fishrock123]

Awesome. When you make the PR I'll go through the issues and find the bunch we have that should be fixed by 1.5.0.

[rvagg]

@Fishrock123 why are you thinking this should be semver-minor?

[Fishrock123]

I think @bnoordhuis said in irc it would be 2.1? if it's not that's also cool.

[bnoordhuis]

Should be fixed by 04cc03b. Closing, holler if I should reopen it.

[jbergstroem]

Since this doesn't seem to touch anything else but deps/ I don't really see why it would warrant a semver-minor.

[19h]

Great, thanks everyone! 🍻

[bnoordhuis]

@jbergstroem libuv is a public and supported part of the API in the sense that add-ons build and link against it.

There haven't been API additions in v1.5.0 so perhaps io.js can get away with a patchlevel bump but that's a little awkward to explain.

[jbergstroem]

@bnoordhuis ah, of course.