Upgrade make-fetch-happen to v5.0.0

[trivikr]

No description provided.

[Turbo87]

I can't find any references to a v5 release at https://github.com/zkat/make-fetch-happen. Do you know what changed between those releases and why it is not part of the repo?

[trivikr]

I've created an issue with the repo at zkat/make-fetch-happen#69

[isaacs]

https://github.com/npm/make-fetch-happen/blob/latest/CHANGELOG.md

[Turbo87]

thanks @isaacs! looks like the breaking change doesn't affect us.

@trivikr we currently have a merge conflict in the yarn.lock file. can you rebase this PR? I guess we might as well migrate to v6.0.0, which was just released two days ago.

[trivikr]

can you rebase this PR? I guess we might as well migrate to v6.0.0, which was just released two days ago.

PR rebased, and upgraded to make-fetch-happen@^6.0.0

[Turbo87]

argh, sorry, their changelog does not mention that Node.js 8 is now required in v6.0.0

[trivikr]

@Turbo87 Can we release lerna-changelog 1.0.0 deprecating Node.js 6.x as suggested in #147 (comment)?

The last 0.x release was in Oct 2018, and a major version bump is due! https://github.com/lerna/lerna-changelog/releases

[Turbo87]

I'm a bit hesitant because Node 8 will be EOL at the end of the year, so we might as well wait until then and then drop Node 8 support as well. 🤔

[trivikr]

I'm a bit hesitant because Node 8 will be EOL at the end of the year, so we might as well wait until then and then drop Node 8 support as well. 🤔

Why not drop Node 8 support in v2.0.0?
This way your clients will have an option to choose whichever version of lerna-changelog they want, based on Node.js version they're using.

[trivikr]

forced update to make-fetch-happen@^5.0.0 version as of now