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.7.0 to 16.8.0.

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

🚨 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

• ❌ ci/circleci: Your tests failed on CircleCI (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.7.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The dependency react was updated from 16.8.0 to 16.8.1.
• The dependency react-dom was updated from 16.8.0 to 16.8.1.

Your tests are still failing with these versions. Compare changes

[greenkeeper]

• The dependency react was updated from 16.8.1 to 16.8.2.
• The dependency react-dom was updated from 16.8.1 to 16.8.2.

Your tests are still failing with these versions. Compare changes

Release Notes for v16.8.2

16.8.2 (February 14, 2019)

React DOM

• Fix ReactDOM.render being ignored inside useEffect. (@gaearon in #14799)
• Fix a crash when unmounting empty portals. (@gaearon in #14820)
• Fix useImperativeHandle to work correctly when no deps are specified. (@gaearon in #14801)
• Fix crossOrigin attribute to work in SVG image elements. (@aweary in #14832)
• Fix a false positive warning when using Suspense with Hooks. (@gaearon in #14821)

React Test Utils and React Test Renderer

• Include component stack into the act() warning. (@threepointone in #14855)