-
Notifications
You must be signed in to change notification settings - Fork 722
upgrade Node 0.11 (currently v0.11.3, should be v0.11.5) #1328
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
Comments
I plan to go an update next week after JRuby Conf :) On 14/08/2013, at 10:31 AM, Mithgol notifications@github.com wrote:
|
Damn, Travis is apparently only running node 0.11.3 - sorry about that. I should've created a PR instead
Really looking forward to this one. We're working on Node 0.11 compatibility updates, but have no way to run CI on it now. |
Still really looking forward to this one! :) v0.11.6 now. |
I've made the (I think) necessary bumps to nodejs in the travis cookbooks and images to push the versions to |
Node |
Will have an update on this soon. On 5/09/2013, at 3:53 AM, Ron Korving notifications@github.com wrote:
|
Thanks 👍 |
How soon exactly? |
Hopefully next week, sorry, we had some changes which took a little longer than expected On 20/09/2013, at 3:40 AM, Ron Korving notifications@github.com wrote:
|
I have updated the node versions we will install, and will start prepping the VMs this week as well as a blog post with information on the changes. Closing this ticket for now. |
You have a weird sense of time :) |
well.. month ago issue was closed, but problem still persist. |
I am sorry for the delay, we had some complications along the way, I am build new VMs for testing right now and a blog post on the update in the works. On 24/10/2013, at 8:36 AM, Mariusz Nowak notifications@github.com wrote:
|
Currently the unstable version of Node.js running on Travis CI is v0.11.3 (26 Jun 2013).
The most recent release of the unstable Node is v0.11.5 (07 Aug 2013).
An upgrade is necessary to test the projects against the most recent Node features, otherwise a test tends to fail (an example of v0.11.4 code failing on v0.11.3).
The text was updated successfully, but these errors were encountered: