-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Borked libuv 1.4.2 update #1621
Comments
@saghul: we need a release to update it ;) |
I plan to release libuv 1.5.0 tonight / tomorrow morning. |
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. |
@Fishrock123 why are you thinking this should be semver-minor? |
I think @bnoordhuis said in irc it would be 2.1? if it's not that's also cool. |
Should be fixed by 04cc03b. Closing, holler if I should reopen it. |
Since this doesn't seem to touch anything else but |
Great, thanks everyone! 🍻 |
@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. |
@bnoordhuis ah, of course. |
Fixes: nodejs#1397 Fixes: nodejs#1512 Fixes: nodejs#1621 Fixes: nodejs#862 PR-URL: nodejs#1646 Reviewed-By: Ben Noordhuis <[email protected]>
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
The text was updated successfully, but these errors were encountered: