-
Notifications
You must be signed in to change notification settings - Fork 467
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
build: remove Node.js 6 from and add Node.js 13 to travis #573
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Still, I'd wonder if it's good to remove the retired LTS version from our test settings. Should the support of this library keep aligned with LTS lifecycles? Since there is no harm to keep an eye on if we break things on lower NAPI_VERSION targets. |
@legendecas maybe we should move those to accepted failures. |
@gabrielschulhof It make sense for me because we could know if we will introduce some kind of breakage even if on the dismissed Node.js version. |
eb61a77
to
5881a15
Compare
@NickNaso OK I changed the PR accordingly. @legendecas, @mhdawson please take another look! |
5881a15
to
3933b1b
Compare
3933b1b
to
6ec1061
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.