konsumer / gatsby-starter-bootstrap-netlify

Bootstrap and netlify CMS starter for Gatsby

Gatsby Bootstrap Netlify Starter

Bootstrap 4, bootswatch and netlify CMS starter for Gatsby

This repo contains an example blog that is built with Gatsby, and Netlify CMS: demo

It follows the JAMstack architecture by using Git as a single source of truth, and Netlify for continuous deployment, and CDN distribution.

Getting Started

Prerequisites

• Node (I recommend using v8.2.0 or higher)
• Gatsby CLI

Run Locally

gatsby new [SITE_DIRECTORY_NAME] https://github.com/konsumer/gatsby-starter-bootstrap-netlify/
cd [SITE_DIRECTORY_NAME]
npm start

Accessing the CMS

Follow the Netlify CMS Quick Start Guide to set up authentication, and hosting.

Configuration

Set your site's title in gatsby-config.js. If you set disqus to your ID, it will be used for your comments, set it to false and it will be left out. It's currently set to gatsby-starter-blog, for the demo, but you can set it to your disqus ID. author and authorLink aren't currently used for anything, but maybe later.

Theming

You can quickly load any theme from bootswatch by editing src/layouts/index.scss, and switching out cosmo for one of these:

• cosmo
• cerulean
• cyborg
• darkly
• flatly
• journal
• litera
• lumen
• lux
• materia
• minty
• pulse
• sandstone
• simplex
• sketchy
• slate
• solar
• spacelab
• superhero
• united
• yeti

There's 2 lines to change.

You can also comment/uncomment lines in that file to customize exactly what parts of bootstrap are loaded.

gatsby-starter-bootstrap-netlify's Issues

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

The dependency gatsby-plugin-react-helmet was updated from 3.0.0 to 3.0.1.

🚨 View failing branch.

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

gatsby-plugin-react-helmet 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

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

There have been updates to the gatsby monorepo:

• • The dependency gatsby-link was updated from 2.0.13 to 2.0.14.

• The dependency gatsby-plugin-netlify was updated from 2.0.10 to 2.0.11.
• The dependency gatsby-plugin-offline was updated from 2.0.23 to 2.0.24.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.7 to 3.0.8.
• The dependency gatsby-plugin-sass was updated from 2.0.9 to 2.0.10.
• The dependency gatsby-remark-copy-linked-files was updated from 2.0.8 to 2.0.9.
• The dependency gatsby-remark-prismjs was updated from 3.2.3 to 3.2.4.
• The dependency gatsby-source-filesystem was updated from 2.0.22 to 2.0.23.
• The dependency gatsby-transformer-remark was updated from 2.3.0 to 2.3.1.
• The dependency gatsby was updated from 2.1.24 to 2.1.25.

🚨 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

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

The dependency gatsby was updated from 2.0.17 to 2.0.18.

🚨 View failing branch.

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

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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Commits

The new version differs by 16 commits.

• f016583 chore(release): Publish
• 5386e1d feat(gatsby): switch to different caching mechanism backed by fs (#8435)
• 10bc679 feat: add option to use mozjpeg (#8621)
• 679a4bb feat(www/starters): Update WordPress starter for new maintainer (#8761)
• b0f2104 blog: add web perf 102 blog post relating to Gatsby v2 (#8501)
• 70d041b feat(www/starters) Fix sidebar scroll (#8743)
• 26c251a Added serverless.com to sites.yml (#8746)
• 8c13547 Fixed typo in the repo (#8754)
• 2d04289 fix: fix wording in plopfile (#8735)
• 3c824f3 fix: navigateTo deprecation message (#8745)
• ba5e255 Add deploying-to-heroku.md (#8721)
• db5390d fix(docs): Link to instructions on adding to plugin library (#8686)
• 7279eab updated gatsby-plugin-remove-trailing-slashes docs to include link re… (#8720)
• 6eddf45 feat(www/starters): Add TypeScript and Contentful starter (#8704)
• d1702d2 fix(docs): fix typos in template doc (#8692)

There are 16 commits in total.

See the full diff

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 🌴

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

The dependency gatsby-link was updated from 2.0.1 to 2.0.2.

🚨 View failing branch.

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

gatsby-link 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

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

The dependency gatsby-transformer-remark was updated from 2.1.6 to 2.1.7.

🚨 View failing branch.

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

gatsby-transformer-remark 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

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

The dependency reactstrap was updated from 6.4.0 to 6.5.0.

🚨 View failing branch.

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

reactstrap 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for 6.5.0

6.5.0 (2018-10-04)

Bug Fixes

• boundariesElement: add DOMElement to allowed proptypes (#1238) (cfe7318)
• Dropdown: enter key triggers onClick (#1232) (f2528da), closes #1228
• Modal: do not trigger focus on SVG elements (#1212) (c7e6ef5), closes #1208
• Modal: use static openCount to become resilient to classList modification (#1190) (c8ceeeb), closes #1189
• Tooltip: clear timers on component unmount (#1180) (9fea409)

Features

• Button: add close icon support (#1206) (02f5e9a), closes #1182
• FormGrid: Add form-row (#1237) (205e80d), closes #1195
• Modal: add custom close button (#1168) (5f33a1a)
• Popover/Tooltip: Implented usage of react 16.3 RefObject as target (#1200) (0eade39), closes #1198

Commits

The new version differs by 19 commits.

• 0dc2acd chore(release): adding 6.5.0 (#1247)
• 5b77a14 chore(docs): bumped bootstrap version to 4.1.3
• d85f81a chore(docs): render spaces around ".clearfix" (#1243)
• cfe7318 fix(boundariesElement): add DOMElement to allowed proptypes (#1238)
• 205e80d feat(FormGrid): Add form-row (#1237)
• 02f5e9a feat(Button): add close icon support (#1206)
• bd8b2e0 chore(UncontrolledButtonDropdown): Add docs (#1235)
• f2528da fix(Dropdown): enter key triggers onClick (#1232)
• 35b4dd7 chore(readme): add improved install information (#1220)
• b52f7b3 docs(Collapse): Transition.propTypes (#921) (#1207)
• 0eade39 feat(Popover/Tooltip): Implented usage of react 16.3 RefObject as target (#1200)
• f922b73 test(InputGroupAddon): add missing tests (#1211)
• 28ddb5d test(DropdownMenu): add missing test (#1210)
• c7e6ef5 fix(Modal): do not trigger focus on SVG elements (#1212)
• 6e83cad docs(Form,FormFeedback,FormGroup,FormText): add props section (#1209)

There are 19 commits in total.

See the full diff

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 🌴

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

The dependency gatsby-remark-prismjs was updated from 3.0.1 to 3.0.2.

🚨 View failing branch.

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

gatsby-remark-prismjs 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

Admin page not redirecting after logging in with Netlify Identity Widget.

Great work here! I was able to deploy and access the admin page but after logging in through Netlify it only displays the confirmation window: "Logged in as" but it does not redirect to the actual admin page. I had to refresh the page manually after authorizing to view the admin UI.

I noticed on the [Netlify CMS Docs](https://www.netlifycms.org/docs/quick-start/#authentication) they mentioned placing the redirect script on the main app index page but I'm also seeing it on the admin index file as well on your project, not sure if that is affecting it but I tried swapping it around and ended up breaking the functionality. Let me know if you have any solutions, Thanks!

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

The dependency gatsby-remark-prismjs was updated from 3.0.0 to 3.0.1.

🚨 View failing branch.

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

gatsby-remark-prismjs 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

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

The dependency gatsby-plugin-netlify was updated from 2.0.1 to 2.0.2.

🚨 View failing branch.

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

gatsby-plugin-netlify 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

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

The dependency gatsby-plugin-sass was updated from 2.0.1 to 2.0.2.

🚨 View failing branch.

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

gatsby-plugin-sass 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

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

The dependency gatsby-plugin-offline was updated from 2.0.5 to 2.0.6.

🚨 View failing branch.

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

gatsby-plugin-offline 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

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

The dependency gatsby-transformer-remark was updated from 2.1.3 to 2.1.4.

🚨 View failing branch.

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

gatsby-transformer-remark 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

making a new post from netlifycms is broken

hey, nice template, however it didnt work for me.

first of all it marks the attachment and the related posts as required in the admin. this is probably wrong:

then when you save the post, gatsby just dies and doesnt publish:

12:51:17 PM: Build ready to start
12:51:17 PM: Fetching cached dependencies
12:51:18 PM: Starting to download cache of 123.9MB
12:51:19 PM: Finished downloading cache in 851.220519ms
12:51:25 PM: Preparing Git Reference refs/heads/master
12:51:26 PM: Running build command: gatsby build
12:51:29 PM: v6.12.2 is already installed.
12:51:30 PM: Now using node v6.12.2 (npm v3.10.10)
12:51:30 PM: Using version v6.12.2 of node
12:51:30 PM: Using /opt/buildhome/.rvm/gems/ruby-2.1.2
12:51:31 PM: Installing NPM modules using Yarn version 0.18.1
12:51:32 PM: yarn install v0.18.1
12:51:32 PM: [1/4] Resolving packages...
12:51:33 PM: success Already up-to-date.
12:51:33 PM: Done in 1.24s.
12:51:33 PM: NPM modules installed using Yarn
12:51:35 PM: success delete html files from previous builds — 0.016 s
12:51:35 PM: success open and validate gatsby-config.js — 0.020 s
12:51:35 PM: success copy gatsby files — 0.028 s
12:51:35 PM: success onPreBootstrap — 0.009 s
12:51:35 PM: success source and transform nodes — 0.158 s
12:51:36 PM: success building schema — 0.426 s
12:51:36 PM: success createLayouts — 0.011 s
12:51:36 PM: success createPages — 0.160 s
12:51:36 PM: success createPagesStatefully — 0.018 s
12:51:36 PM: success onPreExtractQueries — 0.001 s
12:51:36 PM: success update schema — 0.228 s
12:51:36 PM: success extract queries from components — 0.203 s
12:51:37 PM: success run graphql queries — 0.091 s
12:51:37 PM: success write out page data — 0.004 s
12:51:37 PM: success write out redirect data — 0.001 s
12:51:37 PM: success onPostBootstrap — 0.001 s
12:51:37 PM: 
12:51:37 PM: info bootstrap finished - 3.391 s
12:51:44 PM: success Building CSS — 7.430 s
12:52:13 PM: success Building production JavaScript bundles — 29.262 s
12:52:19 PM: 
12:52:19 PM: error Building static HTML for pages failed

See our docs page on debugging HTML builds for help https://goo.gl/yL9lND
12:52:19 PM: 
  14 | export default function Template ({ data }) {
  15 |   const { markdownRemark: post } = data
> 16 |   const related = post.frontmatter.related ? post.frontmatter.related.map(r => findNode(r.post, data)) : []
     |                        ^
  17 |   return (
  18 |     <div>
  19 |       <Helmet title={`Blog | ${post.frontmatter.title}`}>


  WebpackError: Cannot read property 'frontmatter' of null
  
  - blog.js:16 Template
    src/templates/blog.js:16:24
  
  - ReactCompositeComponent.js:306 ReactCompositeComponentWrapper._constructComp    onentWithoutOwner
    ~/react-dom/lib/ReactCompositeComponent.js:306:1
  
  - ReactCompositeComponent.js:282 ReactCompositeComponentWrapper._constructComp    onent
    ~/react-dom/lib/ReactCompositeComponent.js:282:1
  
  - ReactCompositeComponent.js:185 ReactCompositeComponentWrapper.mountComponent    ~/react-dom/lib/ReactCompositeComponent.js:185:1
  
  - ReactReconciler.js:43 Object.mountComponent
    ~/react-dom/lib/ReactReconciler.js:43:1
  
  - ReactMultiChild.js:234 ReactDOMComponent.mountChildren
    ~/react-dom/lib/ReactMultiChild.js:234:1
  
  - ReactDOMComponent.js:657 ReactDOMComponent._createContentMarkup
    ~/react-dom/lib/ReactDOMComponent.js:657:1
  
  - ReactDOMComponent.js:524 ReactDOMComponent.mountComponent
    ~/react-dom/lib/ReactDOMComponent.js:524:1
  
  - ReactReconciler.js:43 Object.mountComponent
    ~/react-dom/lib/ReactReconciler.js:43:1
  
  - ReactMultiChild.js:234 ReactDOMComponent.mountChildren
    ~/react-dom/lib/ReactMultiChild.js:234:1
  
12:52:19 PM: Cached NPM modules
12:52:19 PM: Saved Yarn cache
12:52:19 PM: Build complete: exit code: 1
12:52:19 PM: Saved Cache Directory
12:52:19 PM: Cleaning up docker container
12:52:19 PM: Error running command: Build script returned non-zero exit code: 1
12:52:20 PM: An error occurred while building the site, skipping the deploy and cache refresh.
12:52:20 PM: Build script returned non-zero exit code: 1
12:52:22 PM: Finished processing build request in 1m4.761833045s

sorry.

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

There have been updates to the gatsby monorepo:

• • The dependency gatsby-link was updated from 2.0.6 to 2.0.7.

• The dependency gatsby-plugin-netlify was updated from 2.0.5 to 2.0.6.
• 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.3 to 3.0.4.
• The dependency gatsby-plugin-sass was updated from 2.0.4 to 2.0.5.
• The dependency gatsby-remark-copy-linked-files was updated from 2.0.6 to 2.0.7.
• The dependency gatsby-remark-prismjs was updated from 3.1.1 to 3.1.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.14 to 2.1.15.
• The dependency gatsby was updated from 2.0.59 to 2.0.60.

🚨 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

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 🌴

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

The dependency gatsby was updated from 2.0.4 to 2.0.5.

🚨 View failing branch.

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

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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Commits

The new version differs by 12 commits.

• 208547f chore(release): Publish
• 60e1361 Add more default extensions to resolve .mjs & .wasm & .json (#8327)
• 23b8433 deleted docs we decided we don't need anymore (#8281)
• bb765bc Deleted docs per conversation last week (#8329)
• 74c8400 Updated doc with details from other source (#8284)
• 67847bb Draft of v2 release notes to match v1 release notes (#8282)
• 8461817 scripts: fix an issue with the build-examples script (#8295)
• 2a72471 Fixing performance docs (#8328)
• 6cecbb5 [www] Responsive Design/Mobile Layout for Creators Showcase (#8121)
• 07ef15e chore(release): Publish
• d19e812 Fail quietly on screenshot node errors (#8300)
• 49d5ec4 Fix typo (#8308)

See the full diff

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 🌴

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

The dependency gatsby-source-filesystem was updated from 2.0.1 to 2.0.2.

🚨 View failing branch.

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

gatsby-source-filesystem 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

Update code

I need to remake this for latest gatsby & netlify. I think newest gatsby version improves a lot of things, and there are a few changes to netlify that would be good to get in here. Additionally, I could probly improve a few areas, codewise, using react hooks & lazy and other tricks.

related: #41 #43

netlify identity is not working

I have tried to clone this repo and add the site to netlify. The website is up and running but when I go to the my_site/admin and sign up, I get this weird error.

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

There have been updates to the gatsby monorepo:

• • The dependency gatsby-link was updated from 2.0.6 to 2.0.7.

• The dependency gatsby-plugin-netlify was updated from 2.0.5 to 2.0.6.
• 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.3 to 3.0.4.
• The dependency gatsby-plugin-sass was updated from 2.0.4 to 2.0.5.
• The dependency gatsby-remark-copy-linked-files was updated from 2.0.6 to 2.0.7.
• The dependency gatsby-remark-prismjs was updated from 3.1.1 to 3.1.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.14 to 2.1.15.
• The dependency gatsby was updated from 2.0.59 to 2.0.60.

🚨 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

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 🌴

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

There have been updates to the react monorepo:

• • The dependency react was updated from 16.5.2 to 16.6.0.

• The dependency react-dom was updated from 16.5.2 to 16.6.0.

🚨 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 react group definition.

react 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

How to login?

On this admin page: http://localhost:8000/admin/index.html#/

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

The dependency gatsby-plugin-netlify was updated from 2.0.0 to 2.0.1.

🚨 View failing branch.

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

gatsby-plugin-netlify 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

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

The dependency gatsby-link was updated from 2.0.3 to 2.0.4.

🚨 View failing branch.

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

gatsby-link 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

An in-range update of gatsby-remark-copy-linked-files is breaking the build 🚨

The dependency gatsby-remark-copy-linked-files was updated from 2.0.5 to 2.0.6.

🚨 View failing branch.

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

gatsby-remark-copy-linked-files 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴