An in-range update of jest-enzyme is breaking the build 🚨

[greenkeeper]

The devDependency jest-enzyme was updated from 7.1.1 to 7.1.2.

🚨 View failing branch.

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

jest-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

• ❌ Travis CI - Branch: The build errored.

---

Commits

The new version differs by 11 commits ahead by 11, behind by 2.

• abce48f v7.1.2
• 7951364 Changelog 7.1.2
• 8697d81 Use setupFilesAfterEnv instead of setupTestFrameworkScriptFile
• ffb2861 Add second type parameter
• 4e18cb1 Update packages/jest-enzyme/README.md, add changes suggestion.
• 9253e39 Update README.md: fix a link to #tohavedisplayname.
• 271af50 Upgrade Babel to 7.6.2 and Jest to 24.9.0
• 5556aa6 Replace setupTestFrameworkScriptFile with setupFilesAfterEnv in jest-environment-enzyme README.md
• 54dbf3c Replace setupTestFrameworkScriptFile with setupFilesAfterEnv in jest-enzyme README.md
• 66c1937 v7.1.1
• 427710d 7.1.1 Changelog

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]

After pinning to 7.1.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.