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

[Greenkeeper]

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.34 to 2.0.35.

• The dependency gatsby-plugin-feed was updated from 2.0.15 to 2.1.0.
• The dependency gatsby-plugin-google-analytics was updated from 2.0.17 to 2.0.18.
• The dependency gatsby-plugin-manifest was updated from 2.0.23 to 2.0.24.
• The dependency gatsby-plugin-offline was updated from 2.0.24 to 2.0.25.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.10 to 3.0.11.
• The dependency gatsby-plugin-sharp was updated from 2.0.30 to 2.0.31.
• The dependency gatsby-remark-copy-linked-files was updated from 2.0.10 to 2.0.11.
• The dependency gatsby-remark-images was updated from 3.0.9 to 3.0.10.
• The dependency gatsby-remark-prismjs was updated from 3.2.5 to 3.2.6.
• The dependency gatsby-remark-responsive-iframe was updated from 2.1.0 to 2.1.1.
• The dependency gatsby-remark-smartypants was updated from 2.0.8 to 2.0.9.
• The dependency gatsby-source-filesystem was updated from 2.0.27 to 2.0.28.
• The dependency gatsby-transformer-remark was updated from 2.3.7 to 2.3.8.
• The dependency gatsby-transformer-sharp was updated from 2.1.16 to 2.1.17.
• The dependency gatsby was updated from 2.3.1 to 2.3.2.

🚨 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 direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ Travis CI - Branch: The build errored.

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴