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

greenkeeper[bot] commented 4 years ago

There have been updates to the react monorepo:

- The dependency react was updated from 16.12.0 to 16.13.0.
- The dependency react-dom was updated from 16.12.0 to 16.13.0.

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](https://travis-ci.org/uwap/mqtt-control-map/builds/656117648?utm_source=github_status&utm_medium=notification)).

Release Notes for 16.13.0 (February 26, 2020)

React

Warn when a string ref is used in a manner that's not amenable to a future codemod (@lunaruan in #17864)
Deprecate React.createFactory() (@trueadm in #17878)

React DOM

Warn when changes in style may cause an unexpected collision (@sophiebits in #14181, #18002)
Warn when a function component is updated during another component's render phase (@acdlite in #17099)
Deprecate unstable_createPortal (@trueadm in #17880)
Fix onMouseEnter being fired on disabled buttons (@AlfredoGJ in #17675)
Call shouldComponentUpdate twice when developing in StrictMode (@bvaughn in #17942)
Add version property to ReactDOM (@ealush in #15780)
Don't call toString() of dangerouslySetInnerHTML (@sebmarkbage in #17773)
Show component stacks in more warnings (@gaearon in #17922, #17586)

Concurrent Mode (Experimental)

Warn for problematic usages of ReactDOM.createRoot() (@trueadm in #17937)
Remove ReactDOM.createRoot() callback params and added warnings on usage (@bvaughn in #17916)
Don't group Idle/Offscreen work with other work (@sebmarkbage in #17456)
Adjust SuspenseList CPU bound heuristic (@sebmarkbage in #17455)
Add missing event plugin priorities (@trueadm in #17914)
Fix isPending only being true when transitioning from inside an input event (@acdlite in #17382)
Fix React.memo components dropping updates when interrupted by a higher priority update (@acdlite in #18091)
Don't warn when suspending at the wrong priority (@gaearon in #17971)
Fix a bug with rebasing updates (@acdlite and @sebmarkbage in #17560, #17510, #17483, #17480)

Artifacts

react: https://unpkg.com/react@16.13.0/umd/
react-art: https://unpkg.com/react-art@16.13.0/umd/
react-dom: https://unpkg.com/react-dom@16.13.0/umd/
react-is: https://unpkg.com/react-is@16.13.0/umd/
react-test-renderer: https://unpkg.com/react-test-renderer@16.13.0/umd/
scheduler: https://unpkg.com/scheduler@0.19.0/umd/

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 4 years ago

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

greenkeeper[bot] commented 4 years ago

The dependency react was updated from 16.13.0 to 16.13.1.
The dependency react-dom was updated from 16.13.0 to 16.13.1.

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

uwap / mqtt-control-map