-
Notifications
You must be signed in to change notification settings - Fork 166
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
update nodegyp-test-pull-request
#747
Comments
I wasn't planning on maintaining branches for v0.10 and v0.12 once we bump major. Was anyone else and if so, why? |
I believe that takes care of it, so I'll close. Please reopen if I missed something. |
nodejs/node-gyp#1212 (comment) If someone finds a new bug (especially on Windows, "Windows user are not happy" and all that Jazz) 🤷♂️ personally I have no problem helping them. |
Re: nodejs/node-gyp@75cfae2 |
I think the right statement is "we might consider doing another release on a case-by-case basis". |
Re: nodejs/node-gyp#1212
node8
to the fannode-gyp@4.x.x
we will only support node >= 4node-gyp@3
will go into "LTS"So I assume we need a matrix?
The text was updated successfully, but these errors were encountered: