chore: upgrade to node 12.13

[wardpeet]

Description

Upgraded all packages to node 12 and bumped all peerdeps

Using the following config in Lerna to keep minors below 1

versions.set('gatsby-admin', '0.10.0-next.0');
versions.set('gatsby-plugin-graphql-config', '0.9.0-next.0');
versions.set('gatsby-recipes', '0.11.0-next.0');
versions.set('gatsby-theme', '0.10.0-next.0');

[thibaudcolas]

Just commenting to say I’m surprised this was marked as a chore in conventional-commits terminology, and as such this change wasn’t surfaced in the gatsby-cli CHANGELOG, where I would expect the information to be. I would have expected changing the supported Node version to be a breaking change – particularly since gatsby-cli’s recommended install method is npm install -g gatsby-cli.

For my project upgrading from Node 10 to Node 12 isn’t an immediate option, so it’s pretty important to know what version of gatsby-cli to install that will work with it.

Anyway, npm install -g gatsby-cli@2 worked for me, installing v2.19.2 of the CLI.

[wardpeet]

Hey,

We bumped node 10 - 12 during a major. At least it should have 😬 Don't you get an error when doing it on a wrong ndoe version?

[thibaudcolas]

I do, but there is no mention of when the version bump happened that I could see (and the error message doesn't say either), so I resorted to trying all of the minor releases one after the other until I reached v2.