An in-range update of react is breaking the build 🚨

[greenkeeper]

There have been updates to the react monorepo:

• • The dependency react was updated from 16.6.1 to 16.6.2.

• The dependency react-dom was updated from 16.6.1 to 16.6.2.

🚨 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 react group definition.

react 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (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 🌴

[greenkeeper]

After pinning to 16.6.1 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper]

• The dependency react was updated from 16.6.2 to 16.6.3.
• The dependency react-dom was updated from 16.6.2 to 16.6.3.

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

[greenkeeper]

• The dependency react was updated from 16.6.3 to 16.7.0.
• The dependency react-dom was updated from 16.6.3 to 16.7.0.

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

Release Notes for v16.7.0

React DOM

• Fix performance of React.lazy for large numbers of lazily-loaded components. (@acdlite in #14429)
• Clear fields on unmount to avoid memory leaks. (@trueadm in #14276)
• Fix bug with SSR and context when mixing react-dom/server@16.6 and react@<16.6. (@gaearon in #14291)
• Fix a performance regression in profiling mode. (@bvaughn in #14383)

Scheduler (Experimental)

• Post to MessageChannel instead of window. (@acdlite in #14234)
• Reduce serialization overhead. (@developit in #14249)
• Fix fallback to setTimeout in testing environments. (@bvaughn in #14358)
• Add methods for debugging. (@mrkev in #14053)