-
Notifications
You must be signed in to change notification settings - Fork 4
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 enzyme is breaking the build 🚨 #74
Comments
After pinning to 3.7.0 your tests are passing again. Downgrade this dependency 📌. |
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 |
There have been updates to the enzyme monorepo:
devDependency
enzyme was updated from3.7.0
to3.8.0
.devDependency
enzyme-adapter-react-16 was updated from1.7.0
to1.7.1
.🚨 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 enzyme group definition.
enzyme is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
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: