Update Node.js to v10.15

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
circleci/node	docker	minor	10.13 -> 10.15

See full list of changes here.

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot. View repository job log here.

[zephraph]

Interesting.. I didn't realize this would happen. We have to be cautious with this upgrade because we know that 10.14 causes some issues. @joeyAghion it'd probably be good to look to see if they fixed that issue or if it's still around.

[alloy]

:ceiling-cat: Links to context when referring to known issues would be much appreciated 🙏

[joeyAghion]

We definitely have to be cautious with this upgrade. The corresponding ticket is https://artsyproduct.atlassian.net/browse/PLATFORM-1102, but #3235 was eventually necessary to get things healthy again (as well as artsy/metaphysics#1451 on Metaphysics).

I would review the diff carefully and default to not upgrading unless there are explicit fixes for handling of long-lived TCP connections.

[alloy]

default to not upgrading unless there are explicit fixes

Agreed. I would also suggest disabling PRs for dependencies like these.

[zephraph]

Looking back at the 14 docs, it looks like there’s a config setting for lengthening the timeout of http requests. server.headersTimeout

https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#notable-changes-4

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (10.15). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.