-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of gatsby is breaking the build 🚨 #14
Comments
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 469 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 469 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 469 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 469 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 469 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 469 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 469 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 469 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 469 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 469 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 479 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 485 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 502 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 512 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 514 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 519 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 532 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 273 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 299 commits.
There are 250 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 CommitsThe new version differs by 328 commits.
There are 250 commits in total. See the full diff |
Your tests are still failing with these versions. Compare changes |
Your tests are still failing with these versions. Compare changes |
Your tests are still failing with these versions. Compare changes |
Your tests are still failing with these versions. Compare changes |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
Your tests are passing again with this update. Explicitly upgrade to these versions 🚀 |
There have been updates to the gatsby monorepo:
dependency
gatsby-plugin-sharp was updated from2.0.28
to2.0.29
.dependency
gatsby-source-filesystem was updated from2.0.26
to2.0.27
.peerDependency
gatsby was updated from2.1.33
to2.1.34
.🚨 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
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 🌴
The text was updated successfully, but these errors were encountered: