Update gatsby monorepo

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
babel-preset-gatsby	0.6.0 -> 0.11.0
gatsby (changelog)	2.26.0 -> 2.31.1
gatsby-image	2.5.0 -> 2.10.0
gatsby-plugin-manifest	2.6.0 -> 2.11.0
gatsby-plugin-react-helmet	3.4.0 -> 3.9.0
gatsby-plugin-sharp	2.8.0 -> 2.13.1
gatsby-plugin-sitemap	2.6.0 -> 2.11.0
gatsby-plugin-styled-components	3.4.0 -> 3.9.0
gatsby-transformer-sharp	2.6.0 -> 2.11.0

---

Release Notes

gatsbyjs/gatsby

### [`v0.11.0`](https://togithub.com/gatsbyjs/gatsby/releases/v0.11.0) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/v0.10.0...v0.11.0) The headliner of this release is you can now inline CSS in the `` of your site. This is a best practice recommended by Google's AMP project among others as you then avoid additional requests which can signifcantly slow down your site. Testing using webpagetest.org showed that moving css inline improved the Speed Index 20-50%!! In one test on a simulated 3G connection, the time to initial render went from [~1.8 seconds](http://www.webpagetest.org/result/160508_FF_8WW/) to [~1 second](http://www.webpagetest.org/result/160508_95_8YQ/). It's a very simple switch to make. See this commit in the default starter [gatsbyjs/gatsby-starter-default@`1faecb5`](https://togithub.com/gatsbyjs/gatsby-starter-default/commit/1faecb5a7ded5585b12e8330f9aaa663f9d8b769) It's also documented at #### Breaking changes - `post-build.js` moved inside `gatsby-node.js`. If you had added a `post-build.js` module to your code, this function should now be exported from `gatsby-node.js`. A simple way to make the change is to simply require `post-build.js` there e.g. `exports.postBuild = require('./post-build')`. Thanks to [@​LukeSheard](https://togithub.com/LukeSheard) for this! [#​273](https://togithub.com/gatsbyjs/gatsby/issues/273) - The "stages" were renamed. If you override Webpack configs and are switching behavior based on the stage, `static` is split into two stages, `build-css` and `build-html` and `production` is now `build-javascript`. We think these are much more sensible names. Thanks to [@​scottnonnenberg](https://togithub.com/scottnonnenberg) for the this! [#​253](https://togithub.com/gatsbyjs/gatsby/issues/253) #### Other notable non-breaking changes [@​benstepp](https://togithub.com/benstepp) did a deep refactor of how we're loading Babel plugins. There shouldn't be any breaking changes but it fixes a number of bugs [#​279](https://togithub.com/gatsbyjs/gatsby/pull/279) Some highlights: - User can override the `.babelrc` passed to webpack. - User can use whatever babel plugins they want. - User babel config is extended with `react-hmre` rather than being overwritten in develop.js. - Object.assign is now polyfilled by default. - Non breaking change as starters previously required a babelrc and gatsby will just read them as normal. - Fixes three issues [#​129](https://togithub.com/gatsbyjs/gatsby/issues/129), [#​235](https://togithub.com/gatsbyjs/gatsby/issues/235), [#​264](https://togithub.com/gatsbyjs/gatsby/issues/264) ### [`v0.10.0`](https://togithub.com/gatsbyjs/gatsby/releases/v0.10.0) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/v0.9.1...v0.10.0) Thanks to the efforts of [@​patrykkopycinski](https://togithub.com/patrykkopycinski), Gatsby now supports React 15. This should be an easy upgrade for most people as long as your current site is showing deprecation warnings in the console.log. [#​252](https://togithub.com/gatsbyjs/gatsby/pull/252) [@​alampros](https://togithub.com/alampros) also contributed a bug fix as he noticed that when setting the host option for `gatsby develop` and `gatsby serve-build` that the short version `-h` overrode the default help option. He changed that to `-H` so there would no longer be a conflict [#​247](https://togithub.com/gatsbyjs/gatsby/pull/247). ### [`v0.9.1`](https://togithub.com/gatsbyjs/gatsby/releases/v0.9.1) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/v0.9.0...v0.9.1) ### New tests! [@​benstepp](https://togithub.com/benstepp) [waded into the center of Gatsby and refactored one of the core functions](https://twitter.com/supermoof/status/478322429257715712) AND setup a test framework AND added a number of tests. Awesome! [#​232](https://togithub.com/gatsbyjs/gatsby/pull/232) ### Bug fixes - [@​BerkeleyTrue](https://togithub.com/BerkeleyTrue) fixed route => template matching which was broken for some edge cases [#​230](https://togithub.com/gatsbyjs/gatsby/pull/230) - [@​BerkeleyTrue](https://togithub.com/BerkeleyTrue) pointed out that errors in `gatsby-node.js` were being swallowed. [@​kyleamathews](https://togithub.com/kyleamathews) fixed that in [`859e412`](https://togithub.com/gatsbyjs/gatsby/commit/859e412211364a56ed61da80f43268809d4c9ed9) - The Autoprefixer plugin was being added to the Postcss multiple times which [@​kyleamathews](https://togithub.com/kyleamathews) fixed in [`dd2e960`](https://togithub.com/gatsbyjs/gatsby/commit/dd2e960bc05cbc2e9a708f71bff16b16d91e5b0c) ### Developer Experience (DX) improvements - [@​michaeljdeeb](https://togithub.com/michaeljdeeb) added a check that hard-coded paths in pages have a path prefix. This is a problem that's bit several people as it's easy to miss [#​223](https://togithub.com/gatsbyjs/gatsby/pull/223). Invariants are awesome! - [@​alehlopeh](https://togithub.com/alehlopeh) added a new cli command `gatsby serve-build` so you can easily check that your built site is working as expected. [#​237](https://togithub.com/gatsbyjs/gatsby/pull/237) Thanks everyone! ### [`v0.9.0`](https://togithub.com/gatsbyjs/gatsby/releases/v0.9.0) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/v0.8.0...v0.9.0) Another release with two nice DX improvements. Also we hit 2500 stars as I was writing this review :tada: #### Babel 6 Gatsby started its life on Babel 5 but Babel 6 is out and stable so we'll upgrade along with the rest of the ecosystem and take advantage of [its improved performance and awesome new plugin api](https://babeljs.io/blog/2015/10/29/6.0.0). #### Gatsby must now be installed as a dependency of the site The global Gatsby install now defers to the local install of Gatsby (and throws if it can't find one). This means you can build a site and not worry about needing to upgrade it again as Gatsby accumulates breaking changes. This also helps ensure Gatsby works in environments where you don't want a global install e.g. build servers. ##### Upgrade instructions - Install Gatsby — `npm install --save gatsby` - Install new Babel 6 dependencies (they must be installed locally) — `npm install --save babel-plugin-add-module-exports babel-preset-es2015 babel-preset-react babel-preset-stage-1` and `npm install --save-dev babel-preset-react-hmre`. - Uninstall old Babel 5 dependencies (if you added any). - The `link` function from `gatsby-helpers.js` was renamed to `prefixLink` to clarify its purpose. - Your `.babelrc` file needs to be upgraded to look like: { "presets": ['react', 'es2015', 'stage-1'], "plugins": ['add-module-exports'] } - If you modified the default Webpack config in `gatsby.config.js`, this functionality is now moved to `gatsby-node.js` and instead of using module.exports, export your config modification function as `modifyWebpackConfig`. See the [updated instructions in the README](https://togithub.com/gatsbyjs/gatsby#how-to-use-your-own-webpack-loaders). - If you were differentiating between pages with content (like .md files) and pages without (like pages/profile.js) by looking for truthy `page.data`, you'll now need check for truthy `page.data.body`. - If your site is under version control, you might want to ignore the new auto-written module `.gatsby-context.js`. - **rare** if you used the `rewritePath`, `onRouteChange` hooks in your app.js — app.js is now not supported. Instead you should export `rewritePath` in `gatsby-node.js` and `onRouteChange` in `gatsby-browser.js`. The function signatures didn't change. These new files will be gaining more functionality in future releases. That's it! See you in the issue queues :-) ### [`v0.8.0`](https://togithub.com/gatsbyjs/gatsby/compare/v0.7.0...v0.8.0) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/v0.7.0...v0.8.0) ### [`v0.7.0`](https://togithub.com/gatsbyjs/gatsby/releases/v0.7.0) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/135e554aa9e8f10a282983eca65c29ffae738339...v0.7.0) ##### Update to React 0.14 The big change for this release was updating React to 0.14. Thanks to [@​patrykkopycinski](https://togithub.com/patrykkopycinski) for his [PR](https://togithub.com/gatsbyjs/gatsby/pull/81)! We're still on the 0.13 series of React Router as their recent 1.0 release will require internal updates to Gatsby. Follow along at [#​32](https://togithub.com/gatsbyjs/gatsby/issues/32) if interested. #### `gatsby serve` now `gatsby develop` Serve implied Gatsby was just serving up files. Develop conveys the idea better that you're starting up a full-fledged development server with the intent to start developing. #### Can now do webpack requires in your html.jsx Previously you couldn't do webpack requires in your html component as the development server was requiring the module in node context. But with the help of [@​petehunt](https://togithub.com/petehunt)'s [webpack-require](https://togithub.com/petehunt/webpack-require) project, you can now require css or anything else you'd like in your html.jsx. #### Improved support for prefixing site links e.g. when building for Github Pages. [See the documentation that's been added to the README.](https://togithub.com/gatsbyjs/gatsby#deploying-to-github-pages-and-other-times-your-sites-links-need-prefixes) ### How to upgrade You'll need to update React in your project to React 0.14 as well as upgrade any React components that relied on older React APIs. Make sure to _not_ install the latest react-router.

---

Renovate configuration

:date: Schedule: "after 10pm every weekday,before 5am every weekday" (UTC).

:vertical_traffic_light: Automerge: Enabled.

:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[renovate[bot]]

Branch automerge failure

This PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[vercel[bot]]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/willthevideoman/willhall-uk/4mkwy6fiw
✅ Preview: https://willhall-uk-git-renovate-gatsby-monorepo.willthevideoman.vercel.app

[Deployment for b614488 failed]