Skip to content

Force node 4.3 #347

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

Merged
merged 2 commits into from
Feb 11, 2016
Merged

Force node 4.3 #347

merged 2 commits into from
Feb 11, 2016

Conversation

drew-gross
Copy link
Contributor

Node 4.1 has a security vulnerability. Lets update our Node.

https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/

Node 4.1 has a security vulnerability. Lets update our Node.

https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/
@nlutsenko
Copy link
Contributor

@drew-gross can we update Travis-CI as well? It's running old node right now.

@drew-gross drew-gross assigned nlutsenko and unassigned drew-gross Feb 10, 2016
@facebook-github-bot
Copy link

@drew-gross updated the pull request.

@nlutsenko
Copy link
Contributor

Wondeful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants