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

Question

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

Closed this issue 6 years ago · 8 comments

Version 16.4.2 of the react packages was just published.

Branch	Build failing 🚨
Monorepo release group	react
Current Version	16.4.1
Type	devDependency

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).

Release Notes

v16.4.2

16.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 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)

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 🌴

Answer 1 · 2018-08-01T21:37:29.000Z

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.

Answer 2 · 2018-09-06T19:27:54.000Z

Version 16.5.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 3 · 2018-09-14T01:45:23.000Z

The devDependency react was updated from 16.5.0 to 16.5.1.
The devDependency react-dom was updated from 16.5.0 to 16.5.1.
The devDependency react-test-renderer was updated from 16.5.0 to 16.5.1.

Your tests are still failing with these versions. Compare changes

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 with schedule/tracking. (@bvaughn in #13605)
If a ForwardRef component defines a displayName, use it in warnings. (@probablyup in #13615)

Schedule (Experimental)

Add a separate profiling entry point at schedule/tracking-profiling. (@bvaughn in #13605)

Answer 4 · 2018-09-19T05:09:14.000Z

The devDependency react was updated from 16.5.1 to 16.5.2.
The devDependency react-dom was updated from 16.5.1 to 16.5.2.
The devDependency react-test-renderer was updated from 16.5.1 to 16.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)

Renaming "tracking" API to "tracing" (@bvaughn in #13641)
Add UMD production+profiling entry points (@bvaughn in #13642)
Refactored schedule to remove some React-isms and improve performance for when deferred updates time out (@acdlite in #13582)

Answer 5 · 2018-10-24T00:42:16.000Z

The devDependency react was updated from 16.5.2 to 16.6.0.
The devDependency react-dom was updated from 16.5.2 to 16.6.0.
The devDependency react-test-renderer was updated from 16.5.2 to 16.6.0.

Your tests are still failing with these versions. Compare changes

Answer 6 · 2018-11-07T07:14:25.000Z

The devDependency react was updated from 16.6.0 to 16.6.1.
The devDependency react-dom was updated from 16.6.0 to 16.6.1.
The devDependency react-test-renderer was updated from 16.6.0 to 16.6.1.

Your tests are still failing with these versions. Compare changes

Release Notes for v16.6.1

16.6.1 (November 6, 2018)

React DOM

Fallback should not remount every time a promise resolves. (@acdlite in #14083)
Fix bug where Suspense keeps showing fallback even after everything finishes loading. (@acdlite in #14083)
Fix unresolved default props in lifecycle methods of a lazy component. (@gaearon in #14112)
Fix bug when recovering from an error thrown during complete phase. (@gaearon in #14104)

Scheduler (Experimental)

Switch from deadline object to shouldYield API. (@acdlite in #14025)

Answer 7 · 2018-11-13T03:01:43.000Z

The devDependency react was updated from 16.6.1 to 16.6.2.
The devDependency react-dom was updated from 16.6.1 to 16.6.2.
The devDependency react-test-renderer was updated from 16.6.1 to 16.6.2.

Your tests are still failing with these versions. Compare changes

Answer 8 · 2018-11-13T05:41:11.000Z

The devDependency react was updated from 16.6.2 to 16.6.3.
The devDependency react-dom was updated from 16.6.2 to 16.6.3.
The devDependency react-test-renderer was updated from 16.6.2 to 16.6.3.

Your tests are still failing with these versions. Compare changes