An in-range update of gatsby is breaking the build 🚨
greenkeeper opened this issue · 1 comments
greenkeeper commented
The dependency gatsby was updated from 2.0.34
to 2.0.35
.
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 could not complete due to an error (Details).
Commits
The new version differs by 20 commits.
ce24780
chore(release): Publish
6cb7762
Feature: placeholderClass prop for gatsby-image (#9187)
49d4da1
Add start script to package.json in gatsby/examples/* (#9570)
ba5aa4d
Minor typo corrections for gatsby-style-guide.md (#9510)
5fc3d15
Edit sites.yml. Edit Caddy smells like trees (#9278)
6bbc4f0
docs: add section on multiple layouts to gatsby-layout-plugin docs (#9538)
43c1264
Update index.md (#9562)
f2ac164
Fix consistency with "and" rather than ampersands and usage of serial… (#9546)
93dfe10
docs: fill out static folder stub (#9287)
dc867db
minor grammatical fixes (#9530)
886840c
feat(starters): add mhadaily/gatsby-starter-typescript-power-blog (#9519)
795988b
fix(www): Containter component may have class: 'undefined'. (#9537)
c62556e
feat(starters): add gatsby-starter-calpa-blog (#9541)
ea7bd6b
feat(starters): add gatsby-starter-i18n-blog (#9545)
b5b43d5
fix(gatsby): fix crash on inferring input type with missing node (#9487)
There are 20 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 🌴
greenkeeper commented
After pinning to 2.0.34 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.