-
Notifications
You must be signed in to change notification settings - Fork 31
Node v0.11 support #16
Comments
+1 |
1 similar comment
+1 |
+1 |
While we will eventually add the support for v0.11, if someone wants to contribute and submit a PR for it, it would go a long way! Cheers! |
I have started to play with the new v8 API seems there were quite big changes the WIP branch is here: https://github.com/apiaryio/protagonist/tree/zdne/node-v0.11-support New Node documentation available here: https://github.com/joyent/node/blob/v0.11.14-release/doc/api/addons.markdown |
+1 (this should also add support for iojs 1.x) |
Will just add this now happens on the new Node.js 0.12 release |
+1 |
@zdne Hmm, will this make the "new" protagonist versions backward-incompatible with 0.10? |
@Almad I am looking at https://github.com/rvagg/nan using which we can still be backward compatible |
protagonist-experimental@0.18.7 now supports node.js ~0.8.15, 0.10.x, 0.11.x, 0.12.x and io.js v1.x.x |
👍 |
@pksunkara you can't close this issue until it was released as protagonist 👎 |
Is there an ETA for fix on this issue? It's the one thing stopping us from moving to 0.12 or io.js and I'm about to drop it if need be. |
@michaelgilley It has been fixed and beta released at |
Great! Thank you! |
+1 |
+1 |
Any ETA for an official release? |
@jwhitehorn less than two weeks |
Until then please use |
Can you release it as a pre-release tag until then? https://github.com/npm/node-semver#prerelease-tags that way I can manually update sub-dependancies and have it still satisfy the version |
+1 to a pre-release |
Yeah, pre-release would be much nicer |
We are looking into this. Either we will have stable release this week or we will switch to the pre-release. Thanks for your patience. |
We have released a pre-release of protagonist version
|
the latest protagonist |
Also see http://stackoverflow.com/questions/22763774/jenkins-dredd-npm-err-failed-at-the-protagonist0-8-0-install-script?noredirect=1#comment35235905_22763774
The text was updated successfully, but these errors were encountered: