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: dropped node 8 support #441

Merged
merged 2 commits into from
Jul 21, 2020
Merged

Conversation

ruppysuppy
Copy link
Contributor

Issue #437:

Dropped Node 8 support by modifying package.json and .travis.yml files

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@dbanksdesign dbanksdesign changed the base branch from master to 3.0 July 20, 2020 16:50
Copy link
Member

@dbanksdesign dbanksdesign left a comment

Choose a reason for hiding this comment

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

Thank you for this contribution!

I'm thinking we should drop Node 10 as well and be on Node 12 as Node 10 is currently is in "maintenance" and 12 is "active" for now. Could we also add Node 14 in the travis yaml file? What do you think?

Also, I switched the branch to our 3.0 branch because dropping support for Node 8 is a breaking change. The 3.0 release will include some other major features so I thought it was best to group them under one major version release.

@ruppysuppy ruppysuppy requested a review from dbanksdesign July 21, 2020 04:20
@ruppysuppy ruppysuppy changed the title fix: dropped node 8 support chore: dropped node 8 support Jul 21, 2020
Copy link
Member

@dbanksdesign dbanksdesign left a comment

Choose a reason for hiding this comment

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

LGTM! Thank you!

@dbanksdesign dbanksdesign merged commit de11808 into amzn:3.0 Jul 21, 2020
dbanksdesign pushed a commit that referenced this pull request Oct 5, 2020
* Added node v14 in .travis.yml + bumped up nodejs to v12 (package.json)
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