-
Notifications
You must be signed in to change notification settings - Fork 22
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 🚨 #43
Comments
After pinning to 2.0.11 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
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 🚀 CommitsThe new version differs by 4 commits.
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 23 commits.
There are 23 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 25 commits.
There are 25 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 🚀 |
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 🚀 CommitsThe new version differs by 31 commits.
There are 31 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 still failing with these versions. Compare changes CommitsThe new version differs by 57 commits.
There are 57 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 CommitsThe new version differs by 848 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 still failing with these versions. Compare changes CommitsThe new version differs by 2170 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 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 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 still failing with these versions. Compare changes CommitsThe new version differs by 2281 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 still failing with these versions. Compare changes |
There have been updates to the gatsby monorepo:
dependency
gatsby-link was updated from2.0.13
to2.0.14
.dependency
gatsby-plugin-netlify was updated from2.0.10
to2.0.11
.dependency
gatsby-plugin-offline was updated from2.0.23
to2.0.24
.dependency
gatsby-plugin-react-helmet was updated from3.0.7
to3.0.8
.dependency
gatsby-plugin-sass was updated from2.0.9
to2.0.10
.dependency
gatsby-remark-copy-linked-files was updated from2.0.8
to2.0.9
.dependency
gatsby-remark-prismjs was updated from3.2.3
to3.2.4
.dependency
gatsby-source-filesystem was updated from2.0.22
to2.0.23
.dependency
gatsby-transformer-remark was updated from2.3.0
to2.3.1
.dependency
gatsby was updated from2.1.24
to2.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
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: