An in-range update of gatsby is breaking the build 🚨

[greenkeeper[bot]]

There have been updates to the gatsby monorepo:

• • The devDependency babel-preset-gatsby was updated from 0.1.4 to 0.1.5.
  • The dependency gatsby-image was updated from 2.0.21 to 2.0.22.
  • The dependency gatsby-plugin-manifest was updated from 2.0.10 to 2.0.11.
  • The dependency gatsby-plugin-offline was updated from 2.0.17 to 2.0.18.
  • The dependency gatsby-plugin-react-helmet was updated from 3.0.2 to 3.0.3.
  • The dependency gatsby-plugin-sharp was updated from 2.0.13 to 2.0.14.
  • The dependency gatsby-plugin-styled-components was updated from 3.0.3 to 3.0.4.
  • The dependency gatsby-plugin-typescript was updated from 2.0.1 to 2.0.2.
  • The dependency gatsby-source-filesystem was updated from 2.0.9 to 2.0.10.
  • The dependency gatsby-transformer-remark was updated from 2.1.13 to 2.1.14.
  • The dependency gatsby-transformer-sharp was updated from 2.1.8 to 2.1.9.
  • The dependency gatsby was updated from 2.0.58 to 2.0.59.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

- ❌ **coverage/coveralls:** Coverage decreased (-10.5%) to 11.853% ([Details](https://coveralls.io/builds/20362750)). - ✅ **Travis CI - Branch:** The build **passed**, just like the previous build.

---

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree: