Skip to content
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

Merged
merged 1 commit into from
Mar 8, 2016
Merged

[4.1] Bump node to 4.3.2 #6473

merged 1 commit into from
Mar 8, 2016

Conversation

tylersmalley
Copy link
Contributor

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

@rashidkpc
Copy link
Contributor

Looks like esvm can't launch a 1.4.4 cluster to run the tests on this.

@epixa
Copy link
Contributor

epixa commented Mar 8, 2016

@tylersmalley You need that commit I linked you earlier that includes the updated windows binary path.

@tylersmalley
Copy link
Contributor Author

Yeah - I also need to fix the Windows binary location.

@epixa
Copy link
Contributor

epixa commented Mar 8, 2016

985d197

@tylersmalley
Copy link
Contributor Author

@epixa, we're all passing now.

@epixa
Copy link
Contributor

epixa commented Mar 8, 2016

Can you also bump the engine in package.json?

@tylersmalley
Copy link
Contributor Author

@epixa, updated engine

@@ -105,7 +105,7 @@
"tar": "^1.0.1"
},
"engines": {
"node": "~0.10 || ~0.12",
Copy link
Contributor

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?

Copy link
Contributor Author

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>
@w33ble
Copy link
Contributor

w33ble commented Mar 8, 2016

LGTM, planning to merge shortly...

w33ble added a commit that referenced this pull request Mar 8, 2016
@w33ble w33ble merged commit 011daa6 into elastic:4.1 Mar 8, 2016
@tylersmalley tylersmalley deleted the 4.1-node-4.3.2 branch March 8, 2016 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants