-
Notifications
You must be signed in to change notification settings - Fork 168
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
Release 4.1.1 to npm #136
Comments
@dhritzkiv just added you as an owner in NPM — thanks for flagging! Also, great to see movement on the CI front — I tried to figure out how to re-enable Travis at some point, but got tangled and gave up. Now if only we could fix the intermittent AppVeyor failures... |
@mourner Thanks! I'll publish to npm once I upload some prebuilt binaries built into the Github release. And yeah, absolutely no idea what is going on with AppVeyor /Windows |
@dhritzkiv perhaps worth disabling AppVeyor until we figure it out? |
Could be handy so we don't get false negatives during PRs and general pushes. Okay. I'll disable it in the meantime. |
Released! |
Even though I have repo access, I do not appear to have npm access, and therefore cannot push 4.1.1 to npm.
4.1.1 includes:
4.1.1 will also require new precompiled binaries. Ideally, these would be generated and uploaded as part of CI, but I believe uploading is currently broken due to outdated credentials (which I don't have the permissions to upload from Travis to GitHub)
The text was updated successfully, but these errors were encountered: