Open greenkeeper[bot] opened 6 years ago
After pinning to 16.3.2 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 🚨
type
changes from some other types to text
. (@spirosikmd in #12135)event.target
value for the onChange
event in IE9. (@nhunzaker in #12976)<React.Fragment />
from a component. (@philipp-spiess in #12966)Your tests are still failing with this version. Compare the changes 🚨
Fix a potential XSS vulnerability when the attacker controls an attribute name (CVE-2018-6341
). This fix is available in the latest react-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
, and react-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 in react-dom@16.4.2
. (@gaearon in #13303)
Your tests are still failing with this version. Compare the changes 🚨
dependency
react was updated from 16.5.0
to 16.5.1
.dependency
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)dependency
react was updated from 16.5.1
to 16.5.2
.dependency
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 #13643dependency
react was updated from 16.5.2
to 16.6.0
.dependency
react-dom was updated from 16.5.2
to 16.6.0
.Your tests are still failing with these versions. Compare changes
Version 16.4.0 of react was just published.
react
This version is covered by your current version range and after updating it in your project the build failed.
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/LeadingEdgeForum/atlas2/builds/382985566?utm_source=github_status&utm_medium=notification)Release Notes
v16.4.0React
React.unstable_Profiler
component for measuring performance. (@bvaughn in #12745)React DOM
getDerivedStateFromProps()
regardless of the reason for re-rendering. (@acdlite in #12600 and #12802)forwardRef()
on a deepersetState()
. (@gaearon in #12690)propTypes
on a context provider component. (@nicolevy in #12658)react-lifecycles-compat
in<StrictMode>
. (@bvaughn in #12644)forwardRef()
render function haspropTypes
ordefaultProps
. (@bvaughn in #12644)forwardRef()
and context consumers are displayed in the component stack. (@sophiebits in #12777)React Test Renderer
getDerivedStateFromProps()
support to match the new React DOM behavior. (@koba04 in #12676)testInstance.parent
crash when the parent is a fragment or another special node. (@gaearon in #12813)forwardRef()
components are now discoverable by the test renderer traversal methods. (@gaearon in #12725)setState()
updaters that returnnull
orundefined
. (@koba04 in #12756)React ART
React Call Return (Experimental)
React Reconciler (Experimental)
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: