-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Drop Node 4 support in v0.21.0 #1212
Comments
Hey @lovell , first, fantastic lib just started using, switching over from imgmagik & it's doing wonders. It seems this release, while it builds & compiles just fine in Node 9.x it broke our (aws) docker containers' build. After upgrading node locally & our docker node image from 9.5.0 to 10.0.0 everything's kosher on v0.20.1 & 0.20.2. Just wanted to mention in case anyone else ran into the issue. Docker output building v0.20.2 on node v9.5.0:
|
If you drop node 4 maybe it's better to do it in a major version don't you think ? |
@billouboq sharp has yet to reach v1.0.0 so semver allows for "breaking" changes with a minor version increment. By way of example, support for Node 0.10 and 0.12, present in sharp v0.16.2, was dropped in v0.17.0. This was discussed in #610. |
v0.21.0 now available with this change. |
As it will reach "end of life" on the 30th April 2018.
https://github.com/nodejs/Release#release-schedule
The text was updated successfully, but these errors were encountered: