-
Notifications
You must be signed in to change notification settings - Fork 230
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
test(ci): add early supported node versions to test matrix #705
Conversation
@Qard As we discussed yesterday, do you want me to remove |
I'm good either way. |
I should have checked before this last commit - there's no patch releases on the first release of each major version. So this doesn't change a thing 😂 I was just wondering if the failures on Node.js 8.0.0 could be "fixed" by using the newest 8.0.x |
9d431e7
to
3028324
Compare
Early versions of Node.js 8 had a regression around the handling of `null` as the port passed to `Server#listen()`. For details see: nodejs/node#14221
@Qard the bug I fixed in If we later feel that it's too much, we can revisit it and for instance change them to run as a cron job. What do you think about that? |
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. 👍
Early versions of Node.js 8 had a regression around the handling of `null` as the port passed to `Server#listen()`. For details see: nodejs/node#14221
We had an issue where an early version of Node.js v6 didn't have support for a core API we were using. This wasn't caught by our tests because our tests ran on the latest 6.x version.
By adding the first version in each major version range we support to the test matrix, we enhance our ability to catch these issues in the future.