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

chore: remove support for EOL versions of Node.js #2120

Closed
wants to merge 1 commit into from

Conversation

codebytere
Copy link
Member

Description of change

Refs #1945.

Should we also consider moving to GitHub Actions and adding specs for Node.js v14? Feel free to tell me if there's any config code specific to these EOL versions that i missed and i'll ditch it :)

Checklist

@cclauss
Copy link
Contributor

cclauss commented May 12, 2020

Nice initiative. +1 on switching to GitHub Actions. Why the failing tests on Py36?

@codebytere
Copy link
Member Author

codebytere commented May 12, 2020

@cclauss i was seeing a bunch of unexplained macOS GitHub Action runner errors earlier today on other repos too - just gave them another kick but i don't think it's related 🤔 the error showed up like this:

Screen Shot 2020-05-11 at 9 27 10 PM

which frankly is useless enough that it makes me think Actions itself was just struggling

and sounds good - I'll probably follow up with a PR to ditch Travis for Actions if that'd work for y'all

Copy link
Contributor

@cclauss cclauss left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks for doing this.

@cclauss
Copy link
Contributor

cclauss commented May 12, 2020

  • Why not test node_js: 14 ?
  • Why not test dist: focal ?

@rvagg
Copy link
Member

rvagg commented May 13, 2020

741ab09

+1 to Actions, and to adding 14 in there, and switching to Focal, although ubuntu-latest will likely get that for us anyway.

@rvagg rvagg closed this May 13, 2020
@codebytere codebytere deleted the remove-eol-versions branch May 13, 2020 17:36
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.

5 participants