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

[greenkeeper[bot]]

Version 3.5.0 of jest-enzyme just got published.

Branch	Build failing 🚨
Dependency	jest-enzyme
Current Version	3.4.0
Type	devDependency

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

As jest-enzyme is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

Status Details

- ❌ **ci/circleci** CircleCI is running your tests [Details](https://circleci.com/gh/EmmaRamirez/typescript-react-presentation/109?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/EmmaRamirez/typescript-react-presentation/builds/252787399?utm_source=github_status&utm_medium=notification)

---

Release Notes

3.5.0

• Include TS definitions in exported library (@Dean177)
• Fix a bug that can occur when you are mocking console.error in your tests. (@juanca)
• [internal] Use babel-preset-env (@pascalduez)
• [internal] Improve flowtype usage (@pascalduez)

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

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

[greenkeeper[bot]]

Version 3.5.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

[greenkeeper[bot]]

Version 3.5.2 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

3.5.2

• Add the missing export of the toMatchElement assertion (@vkrol)

[greenkeeper[bot]]

Version 3.5.3 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

3.5.3

• Point to lib TS file (@pascalduez)

[greenkeeper[bot]]

Version 3.6.0 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

[greenkeeper[bot]]

Version 3.6.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

[greenkeeper[bot]]

Version 3.7.0 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

[greenkeeper[bot]]

Version 3.8.0 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

3.8.0

• Intentionally passing undefined to toHaveState and toHaveProps now compares on the undefined value. (@DianaSuvorova)

Example:

expect(wrapper).toHaveState('key', undefined);

[greenkeeper[bot]]

Version 3.8.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

[greenkeeper[bot]]

Version 3.8.2 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

[greenkeeper[bot]]

Version 3.8.3 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀