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

Question

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

greenkeeper opened this issue 5 years ago · comments

Greenkeeper commented 5 years ago

There have been updates to the react monorepo:

- The devDependency react was updated from 16.8.6 to 16.9.0.

The devDependency react-dom was updated from 16.8.6 to 16.9.0.
The devDependency react-test-renderer was updated from 16.8.6 to 16.9.0.

🚨 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 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 for 16.9.0 (August 8, 2019)

React

Add <React.Profiler> API for gathering performance measurements programmatically. (@bvaughn in #15172)
Remove unstable_ConcurrentMode in favor of unstable_createRoot. (@acdlite in #15532)

React DOM

Deprecate old names for the UNSAFE_* lifecycle methods. (@bvaughn in #15186 and @threepointone in #16103)
Deprecate javascript: URLs as a common attack surface. (@sebmarkbage in #15047)
Deprecate uncommon "module pattern" (factory) components. (@sebmarkbage in #15145)
Add support for the disablePictureInPicture attribute on <video>. (@eek in #15334)
Add support for onLoad event for <embed>. (@cherniavskii in #15614)
Add support for editing useState state from DevTools. (@bvaughn in #14906)
Add support for toggling Suspense from DevTools. (@gaearon in #15232)
Warn when setState is called from useEffect, creating a loop. (@gaearon in #15180)
Fix a memory leak. (@paulshen in #16115)
Fix a crash inside findDOMNode for components wrapped in <Suspense>. (@acdlite in #15312)
Fix pending effects from being flushed too late. (@acdlite in #15650)
Fix incorrect argument order in a warning message. (@brickspert in #15345)
Fix hiding Suspense fallback nodes when there is an !important style. (@acdlite in #15861 and #15882)
Slightly improve hydration performance. (@bmeurer in #15998)

React DOM Server

Fix incorrect output for camelCase custom CSS property names. (@bedakb in #16167)

React Test Utilities and Test Renderer

Add act(async () => ...) for testing asynchronous state updates. (@threepointone in #14853)
Add support for nesting act from different renderers. (@threepointone in #16039 and #16042)
Warn in Strict Mode if effects are scheduled outside an act() call. (@threepointone in #15763 and #16041)
Warn when using act from the wrong renderer. (@threepointone in #15756)

Artifacts

• react: https://unpkg.com/react@16.9.0/umd/
• react-art: https://unpkg.com/react-art@16.9.0/umd/
• react-dom: https://unpkg.com/react-dom@16.9.0/umd/
• react-is: https://unpkg.com/react-is@16.9.0/umd/
• react-test-renderer: https://unpkg.com/react-test-renderer@16.9.0/umd/
• scheduler: https://unpkg.com/scheduler@0.15.0/umd/

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 🌴

Greenkeeper · Answer 1 · Fri Aug 09 2019 18:45:22 GMT+0800 (China Standard Time)

After pinning to 16.8.6 your tests are passing again. Downgrade this dependency 📌.

Greenkeeper · Answer 2 · Sat Sep 28 2019 06:49:34 GMT+0800 (China Standard Time)

The devDependency react was updated from 16.9.0 to 16.10.0.
The devDependency react-dom was updated from 16.9.0 to 16.10.0.
The devDependency react-test-renderer was updated from 16.9.0 to 16.10.0.

Your tests are still failing with these versions. Compare changes

Greenkeeper · Answer 3 · Sun Sep 29 2019 04:36:51 GMT+0800 (China Standard Time)

The devDependency react was updated from 16.10.0 to 16.10.1.
The devDependency react-dom was updated from 16.10.0 to 16.10.1.
The devDependency react-test-renderer was updated from 16.10.0 to 16.10.1.

Your tests are still failing with these versions. Compare changes

Release Notes for 16.10.1 (September 28, 2019)

React DOM

Fix regression in Next.js apps by allowing Suspense mismatch during hydration to silently proceed (@sebmarkbage in #16943)

Greenkeeper · Answer 4 · Fri Oct 04 2019 08:59:47 GMT+0800 (China Standard Time)

The devDependency react was updated from 16.10.1 to 16.10.2.
The devDependency react-dom was updated from 16.10.1 to 16.10.2.
The devDependency react-test-renderer was updated from 16.10.1 to 16.10.2.

Your tests are still failing with these versions. Compare changes

Release Notes for 16.10.2 (October 3, 2019)

React DOM

Fix regression in react-native-web by restoring order of arguments in event plugin extractors (@necolas in #16978)

Artifacts

• react: https://unpkg.com/react@16.10.2/umd/
• react-art: https://unpkg.com/react-art@16.10.2/umd/
• react-dom: https://unpkg.com/react-dom@16.10.2/umd/
• react-is: https://unpkg.com/react-is@16.10.2/umd/
• react-test-renderer: https://unpkg.com/react-test-renderer@16.10.2/umd/
• scheduler: https://unpkg.com/scheduler@0.16.2/umd/

Greenkeeper · Answer 5 · Wed Oct 23 2019 10:18:15 GMT+0800 (China Standard Time)

The devDependency react was updated from 16.10.2 to 16.11.0.
The devDependency react-dom was updated from 16.10.2 to 16.11.0.
The devDependency react-test-renderer was updated from 16.10.2 to 16.11.0.

Your tests are still failing with these versions. Compare changes

Release Notes for 16.11.0 (October 22, 2019)

React DOM

Fix mouseenter handlers from firing twice inside nested React containers. @yuanoook in #16928
Remove unstable_createRoot and unstable_createSyncRoot experimental APIs. (These are available in the Experimental channel as createRoot and createSyncRoot.) (@acdlite in #17088)

Artifacts

• react: https://unpkg.com/react@16.11.0/umd/
• react-art: https://unpkg.com/react-art@16.11.0/umd/
• react-dom: https://unpkg.com/react-dom@16.11.0/umd/
• react-is: https://unpkg.com/react-is@16.11.0/umd/
• react-test-renderer: https://unpkg.com/react-test-renderer@16.11.0/umd/
• scheduler: https://unpkg.com/scheduler@0.17.0/umd/

Greenkeeper · Answer 6 · Fri Nov 15 2019 10:20:04 GMT+0800 (China Standard Time)

The devDependency react was updated from 16.11.0 to 16.12.0.
The devDependency react-dom was updated from 16.11.0 to 16.12.0.
The devDependency react-test-renderer was updated from 16.11.0 to 16.12.0.

Your tests are still failing with these versions. Compare changes

Greenkeeper · Answer 7 · Fri Feb 28 2020 16:20:11 GMT+0800 (China Standard Time)

The devDependency react was updated from 16.12.0 to 16.13.0.
The devDependency react-dom was updated from 16.12.0 to 16.13.0.
The devDependency react-test-renderer was updated from 16.12.0 to 16.13.0.

Your tests are still failing with these versions. Compare changes

Release Notes for 16.13.0 (February 26, 2020)

React

Warn when a string ref is used in a manner that's not amenable to a future codemod (@lunaruan in #17864)
Deprecate React.createFactory() (@trueadm in #17878)

React DOM

Warn when changes in style may cause an unexpected collision (@sophiebits in #14181, #18002)
Warn when a function component is updated during another component's render phase (@acdlite in #17099)
Deprecate unstable_createPortal (@trueadm in #17880)
Fix onMouseEnter being fired on disabled buttons (@AlfredoGJ in #17675)
Call shouldComponentUpdate twice when developing in StrictMode (@bvaughn in #17942)
Add version property to ReactDOM (@ealush in #15780)
Don't call toString() of dangerouslySetInnerHTML (@sebmarkbage in #17773)
Show component stacks in more warnings (@gaearon in #17922, #17586)

Concurrent Mode (Experimental)

Warn for problematic usages of ReactDOM.createRoot() (@trueadm in #17937)
Remove ReactDOM.createRoot() callback params and added warnings on usage (@bvaughn in #17916)
Don't group Idle/Offscreen work with other work (@sebmarkbage in #17456)
Adjust SuspenseList CPU bound heuristic (@sebmarkbage in #17455)
Add missing event plugin priorities (@trueadm in #17914)
Fix isPending only being true when transitioning from inside an input event (@acdlite in #17382)
Fix React.memo components dropping updates when interrupted by a higher priority update (@acdlite in #18091)
Don't warn when suspending at the wrong priority (@gaearon in #17971)
Fix a bug with rebasing updates (@acdlite and @sebmarkbage in #17560, #17510, #17483, #17480)

Artifacts

react: https://unpkg.com/react@16.13.0/umd/
react-art: https://unpkg.com/react-art@16.13.0/umd/
react-dom: https://unpkg.com/react-dom@16.13.0/umd/
react-is: https://unpkg.com/react-is@16.13.0/umd/
react-test-renderer: https://unpkg.com/react-test-renderer@16.13.0/umd/
scheduler: https://unpkg.com/scheduler@0.19.0/umd/

Greenkeeper · Answer 8 · Fri Mar 20 2020 06:16:48 GMT+0800 (China Standard Time)

The devDependency react was updated from 16.13.0 to 16.13.1.
The devDependency react-dom was updated from 16.13.0 to 16.13.1.
The devDependency react-test-renderer was updated from 16.13.0 to 16.13.1.

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀