-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[4.1] Bump node to 4.3.2 #6473
[4.1] Bump node to 4.3.2 #6473
Conversation
Looks like esvm can't launch a 1.4.4 cluster to run the tests on this. |
@tylersmalley You need that commit I linked you earlier that includes the updated windows binary path. |
Yeah - I also need to fix the Windows binary location. |
f987609
to
2a12a15
Compare
@epixa, we're all passing now. |
Can you also bump the |
2a12a15
to
cc9e9af
Compare
@epixa, updated |
@@ -105,7 +105,7 @@ | |||
"tar": "^1.0.1" | |||
}, | |||
"engines": { | |||
"node": "~0.10 || ~0.12", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can remove iojs from the engines, and also add "npm": "2.14.21"
to it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, will have that updated shortly.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
cc9e9af
to
cf2c1b1
Compare
LGTM, planning to merge shortly... |
This is a major version upgrade of node for the 4.4 line, but it's necessary to fix a memory leak in our ssl implementation.
This release of node upgrades the openssl version to address some security fixes.
See https://nodejs.org/en/blog/release/v4.3.2/
For #6153
Backports #6420