-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Conversation
Thanks. This will currently fail hard. On 4/27/16, Nick Schonning notifications@github.com wrote:
Regards, |
Looks like Appveyor is passing because it doesn't understand the |
Looks like AppVeyor will support it shortly appveyor/ci#770 |
I think the bigger problem is that node-sass just won't compile with node 6 yet. Every major node release invariably means we need to update the C/C++ binding code. At the very least we'll need to update NAN. |
Yeah, someone pointed out in the other tread that NAN is still trying to figure out the issues raised by the depreciation messages. |
To my amazement we compile fine on Node 6. I've started building some binaries. |
Rebased |
Thanks. This is final blocker for 3.7.0. |
Realized that the AppVeyor config was spit between the tag and master builds. I added 6 to the master section and repushed |
Can't wait for |
Looks like node 6 has shipped on appveyor. We have a failing test on node 7 Windows. Will take a closer look tomorrow. It looks race conditiony. |
|
@saper I want to go ahead an ship 3.7.0 with the debug files, which means we don't need to subst. We can retroactively add the debug files when/if nodejs/node#6500 is suitably resolved. Any objections? |
Superseded by #1517 because of timezones. |
Blocked