Open greenkeeper[bot] opened 7 years ago
After pinning to 15.6.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
devDependency
react was updated from 16.5.0
to 16.5.1
.devDependency
react-dom was updated from 16.5.0
to 16.5.1
.Your tests are passing again with this update. Explicitly upgrade to these versions π
React.forwardRef
receives an unexpected number of arguments. (@andresroberto in #13636)isReactComponent
. (@gaearon in #13608)react-dom/profiling
with schedule/tracking
. (@bvaughn in #13605)ForwardRef
component defines a displayName
, use it in warnings. (@probablyup in #13615)devDependency
react was updated from 16.5.1
to 16.5.2
.devDependency
react-dom was updated from 16.5.1
to 16.5.2
.Your tests are passing again with this update. Explicitly upgrade to these versions π
<iframe>
regression (@JSteunou in #13650)updateWrapper
so that <textarea>
s no longer re-render when data is unchanged (@joelbarbosa in #13643devDependency
react was updated from 16.5.2
to 16.6.0
.devDependency
react-dom was updated from 16.5.2
to 16.6.0
.Your tests are passing again with this update. Explicitly upgrade to these versions π
devDependency
react was updated from 16.6.0
to 16.6.1
.devDependency
react-dom was updated from 16.6.0
to 16.6.1
.Your tests are passing again with this update. Explicitly upgrade to these versions π
devDependency
react was updated from 16.6.1
to 16.6.2
.devDependency
react-dom was updated from 16.6.1
to 16.6.2
.Your tests are still failing with these versions. Compare changes
devDependency
react was updated from 16.6.2
to 16.6.3
.devDependency
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 π
devDependency
react was updated from 16.6.3
to 16.7.0
.devDependency
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 π
React.lazy
for large numbers of lazily-loaded components. (@acdlite in #14429)react-dom/server@16.6
and react@<16.6
. (@gaearon in #14291)devDependency
react was updated from 16.7.0
to 16.8.0
.devDependency
react-dom was updated from 16.7.0
to 16.8.0
.Your tests are passing again with this update. Explicitly upgrade to these versions π
devDependency
react was updated from 16.8.0
to 16.8.1
.devDependency
react-dom was updated from 16.8.0
to 16.8.1
.Your tests are passing again with this update. Explicitly upgrade to these versions π
devDependency
react was updated from 16.8.1
to 16.8.2
.devDependency
react-dom was updated from 16.8.1
to 16.8.2
.Your tests are passing again with this update. Explicitly upgrade to these versions π
ReactDOM.render
being ignored inside useEffect
. (@gaearon in #14799)useImperativeHandle
to work correctly when no deps are specified. (@gaearon in #14801)crossOrigin
attribute to work in SVG image
elements. (@aweary in #14832)act()
warning. (@threepointone in #14855)devDependency
react was updated from 16.8.2
to 16.8.3
.devDependency
react-dom was updated from 16.8.2
to 16.8.3
.Your tests are passing again with this update. Explicitly upgrade to these versions π
devDependency
react was updated from 16.8.3
to 16.8.4
.devDependency
react-dom was updated from 16.8.3
to 16.8.4
.Your tests are passing again with this update. Explicitly upgrade to these versions π
Version 15.6.2 of react just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As react 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** Your tests failed on CircleCI [Details](https://circleci.com/gh/react-stream-libs/reactive-renderer/386?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)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: