Closed greenkeeper[bot] closed 5 years ago
After pinning to 16.4.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes π¨
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 still failing with these versions. Compare changes
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 still failing with these versions. Compare changes
<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 still failing with these versions. Compare changes
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 still failing with these versions. Compare changes
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 still failing with these versions. Compare changes
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.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)
Version 16.4.2 of the react packages was just published.
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 devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/Yelp/lemon-reset/builds/410981565?utm_source=github_status&utm_medium=notification)).Release Notes
v16.4.216.4.2 (August 1, 2018)
React DOM Server
Fix a potential XSS vulnerability when the attacker controls an attribute name (
CVE-2018-6341
). This fix is available in the latestreact-dom@16.4.2
, as well as in previous affected minor versions:react-dom@16.0.1
,react-dom@16.1.2
,react-dom@16.2.1
, andreact-dom@16.3.3
. (@gaearon in #13302)Fix a crash in the server renderer when an attribute is called
hasOwnProperty
. This fix is only available inreact-dom@16.4.2
. (@gaearon in #13303)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: