Skip to content
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 .travis.yml to support Node.js 12 #1647

Merged
merged 2 commits into from
Jun 29, 2019
Merged

Conversation

BridgeAR
Copy link
Contributor

This adds Node.js 12 to the test matrix to make sure everything passes as expected.
Node.js 11 is in maintenance and won't receive significant changes anymore, so I updated that as well (no test failures should be accepted).

This adds Node.js 12 to the test matrix to make sure everything passes as expected.
Node.js 11 is in maintenance and won't receive significant changes anymore, so I updated that as well (no test failures should be accepted).
@DABH
Copy link
Contributor

DABH commented May 23, 2019

Thanks @BridgeAR ! Actually, it looks like Node 6 is at long last not supported anymore. So can we also remove Node 6 from travis.yml and appveyor.yml (https://github.com/winstonjs/winston/blob/master/appveyor.yml), and add Node 12 to appveyor.yml too? Then this PR should be good to go (and should pass all CI checks).

Copy link
Contributor

@DABH DABH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed myself; merging away

@DABH DABH merged commit 05bed4d into winstonjs:master Jun 29, 2019
Mizumaki pushed a commit to Mizumaki/winston that referenced this pull request Jun 11, 2020
* Update .travis.yml to support Node.js 12

This adds Node.js 12 to the test matrix to make sure everything passes as expected.
Node.js 11 is in maintenance and won't receive significant changes anymore, so I updated that as well (no test failures should be accepted).

* add n12 on appveyor, remove n6 from travis+appveyor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants