Skip to content

Drop support for Node 4#1145

Merged
gr2m merged 5 commits intomasterfrom
drop-node-4-support
Sep 14, 2018
Merged

Drop support for Node 4#1145
gr2m merged 5 commits intomasterfrom
drop-node-4-support

Conversation

@gr2m
Copy link
Copy Markdown
Member

@gr2m gr2m commented Jun 7, 2018

Node 4 is no longer maintained since April 1, 2018:
https://github.com/nodejs/Release#end-of-life-releases

@gr2m
Copy link
Copy Markdown
Member Author

gr2m commented Jun 7, 2018

ugh I don’t know why tests fail with Node 10 :( If anyone could help to look into it, that’d be great 🙏

@gr2m
Copy link
Copy Markdown
Member Author

gr2m commented Jun 7, 2018

If anyone wants to look into it, it seems to be a problem limited to restify-clients. There is a workaround added for restify which might now be the cause of the problem, it was added a long time ago

Update: should be good now #1148

@gr2m
Copy link
Copy Markdown
Member Author

gr2m commented Jun 14, 2018

I’ll hold off with the major release, there are a few other things I’d like to release as part of v10

@gr2m gr2m changed the title Drop support for Node 4 [WIP] Drop support for Node 4 Jun 14, 2018
@jlilja
Copy link
Copy Markdown
Member

jlilja commented Jul 14, 2018

What is the status on removing Node 4? Is there something still needed to be fixed before the merge?

On a sidenote - Once Node 4 is dropped I'd like to do some refactoring. Would something like that need its own issue or would you just recommend a pr with points on why and how the refactor was made?

@gr2m
Copy link
Copy Markdown
Member Author

gr2m commented Jul 23, 2018

I think I was holding off to see if there are other breaking changes that we can ship with it.

Before doing refactoring, I’d like to finish up the tests first.

  1. finish up Remove AIRPLANE mode for testing - make all tests run offline #1077
  2. Get 100% code coverage (or close to it)

Only when we are confident with our test we can start refactoring, otherwise I’d be really afraid to break peoples code, given how widely used nock is right now. I know fixing the tests on such an old code base is no fun ... do you think you can help out with that?

@gr2m gr2m self-assigned this Sep 14, 2018
@gr2m gr2m force-pushed the drop-node-4-support branch from d03dc34 to 51275a7 Compare September 14, 2018 19:16
BREAKING CHANGE: drop official support for Node 4.

There is no intentional change that breaks usage in Node 4, but as we
stop testing in this no longer supported Node version we recommend to
no update nock if you still rely on Node 4.

The reason why we decided to go ahead and make a breaking version
release is that it became increasingly harder to update dependencies
to the latest versions as they also drop support for Node 4.
@gr2m gr2m force-pushed the drop-node-4-support branch from 51275a7 to 900b85b Compare September 14, 2018 19:19
@gr2m
Copy link
Copy Markdown
Member Author

gr2m commented Sep 14, 2018

I'll merge and release a new breaking version as discussed at #1202

@gr2m gr2m changed the title [WIP] Drop support for Node 4 Drop support for Node 4 Sep 14, 2018
@gr2m gr2m merged commit a7cdc71 into master Sep 14, 2018
@gr2m gr2m deleted the drop-node-4-support branch September 14, 2018 19:37
@nockbot
Copy link
Copy Markdown
Collaborator

nockbot commented Sep 14, 2018

🎉 This PR is included in version 10.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@RichardLitt
Copy link
Copy Markdown
Member

\o/ Thanks, @gr2m!

@lock
Copy link
Copy Markdown

lock bot commented Oct 1, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue and add a reference to this one if it’s related. Thank you!

@lock lock bot locked as resolved and limited conversation to collaborators Oct 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants