An in-range update of react is breaking the build π¨
greenkeeper opened this issue Β· 3 comments
There have been updates to the react monorepoundefined
π¨ 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 failed (Details).
Release Notes for v16.5.1
16.5.1 (September 13, 2018)
React
- Improve the warning when
React.forwardRef
receives an unexpected number of arguments. (@andresroberto in #13636)
React DOM
- Fix a regression in unstable exports used by React Native Web. (@aweary in #13598)
- Fix a crash when component defines a method called
isReactComponent
. (@gaearon in #13608) - Fix a crash in development mode in IE9 when printing a warning. (@link-alex in #13620)
- Provide a better error message when running
react-dom/profiling
withschedule/tracking
. (@bvaughn in #13605) - If a
ForwardRef
component defines adisplayName
, use it in warnings. (@probablyup in #13615)
Schedule (Experimental)
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 π΄
After pinning to 16.5.0 your tests are passing again. Downgrade this dependency π.
- The
dependency
react was updated from16.5.1
to16.5.2
. - The
dependency
react-dom was updated from16.5.1
to16.5.2
.
Your tests are still failing with these versions. Compare changes
Release Notes for v16.5.2
React DOM
- Fixed a recent
<iframe>
regression (@JSteunou in #13650) - Fix
updateWrapper
so that<textarea>
s no longer re-render when data is unchanged (@joelbarbosa in #13643
Schedule (Experimental)
- The
dependency
react was updated from16.5.2
to16.6.0
. - The
dependency
react-dom was updated from16.5.2
to16.6.0
.
Your tests are still failing with these versions. Compare changes