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

upgrade Node 0.11 (currently v0.11.3, should be v0.11.5) #1328

Closed
Mithgol opened this issue Aug 14, 2013 · 13 comments
Closed

upgrade Node 0.11 (currently v0.11.3, should be v0.11.5) #1328

Mithgol opened this issue Aug 14, 2013 · 13 comments

Comments

@Mithgol
Copy link

@Mithgol Mithgol commented Aug 14, 2013

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).

@joshk
Copy link
Contributor

@joshk joshk commented Aug 14, 2013

I plan to go an update next week after JRuby Conf :)

On 14/08/2013, at 10:31 AM, Mithgol 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).


Reply to this email directly or view it on GitHub.

kkoopa referenced this issue in Level/leveldown Aug 16, 2013
Damn, Travis is apparently only running node 0.11.3 - sorry about that.
I should've created a PR instead
@ronkorving
Copy link

@ronkorving ronkorving commented Aug 19, 2013

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.

@ronkorving
Copy link

@ronkorving ronkorving commented Aug 26, 2013

Still really looking forward to this one! :) v0.11.6 now.

@sandfox
Copy link

@sandfox sandfox commented Aug 30, 2013

I've made the (I think) necessary bumps to nodejs in the travis cookbooks and images to push the versions to 0.10.17 and 0.11.6 respectively. Just needs some nice person to merge the PR for travis images and and rebuild the boxes or whatever it is.

travis-ci/travis-cookbooks/pull/214

travis-ci/travis-images/pull/2

@ronkorving
Copy link

@ronkorving ronkorving commented Sep 5, 2013

Node 0.11.7 just got released. Still anxiously awaiting Travis to follow along.

@joshk
Copy link
Contributor

@joshk joshk commented Sep 5, 2013

Will have an update on this soon.

On 5/09/2013, at 3:53 AM, Ron Korving notifications@github.com wrote:

Node 0.11.7 just got released. Still anxiously awaiting Travis to follow along.


Reply to this email directly or view it on GitHub.

@ronkorving
Copy link

@ronkorving ronkorving commented Sep 5, 2013

Thanks 👍

@ronkorving
Copy link

@ronkorving ronkorving commented Sep 20, 2013

How soon exactly?

@joshk
Copy link
Contributor

@joshk joshk commented Sep 20, 2013

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:

How soon exactly?


Reply to this email directly or view it on GitHub.

@joshk
Copy link
Contributor

@joshk joshk commented Sep 22, 2013

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.

@ronkorving
Copy link

@ronkorving ronkorving commented Oct 10, 2013

You have a weird sense of time :)

@medikoo
Copy link

@medikoo medikoo commented Oct 24, 2013

well.. month ago issue was closed, but problem still persist.

@joshk
Copy link
Contributor

@joshk joshk commented Oct 24, 2013

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:

well.. month ago issue was closed, but problem still persist.


Reply to this email directly or view it on GitHub.

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

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.