-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of react is breaking the build 🚨 #780
Comments
Your tests are still failing with these versions. Compare changes |
Your tests are still failing with these versions. Compare changes Release Notes for 16.10.1 (September 28, 2019)React DOM
|
Your tests are still failing with these versions. Compare changes Release Notes for 16.10.2 (October 3, 2019)React DOM
Artifacts• react: https://unpkg.com/[email protected]/umd/ |
Your tests are still failing with these versions. Compare changes Release Notes for 16.11.0 (October 22, 2019)React DOM
Artifacts• react: https://unpkg.com/[email protected]/umd/ |
Your tests are still failing with these versions. Compare changes |
Your tests are still failing with these versions. Compare changes Release Notes for 16.13.0 (February 26, 2020)React
React DOM
Concurrent Mode (Experimental)
Artifacts
|
Your tests are still failing with these versions. Compare changes |
There have been updates to the react monorepo:
dependency
react was updated from16.8.6
to16.9.0
.dependency
react-dom was updated from16.8.6
to16.9.0
.devDependency
react-test-renderer was updated from16.8.6
to16.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 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
Release Notes for 16.9.0 (August 8, 2019)
React
<React.Profiler>
API for gathering performance measurements programmatically. (@bvaughn in #15172)unstable_ConcurrentMode
in favor ofunstable_createRoot
. (@acdlite in #15532)React DOM
UNSAFE_*
lifecycle methods. (@bvaughn in #15186 and @threepointone in #16103)javascript:
URLs as a common attack surface. (@sebmarkbage in #15047)disablePictureInPicture
attribute on<video>
. (@eek in #15334)onLoad
event for<embed>
. (@cherniavskii in #15614)useState
state from DevTools. (@bvaughn in #14906)setState
is called fromuseEffect
, creating a loop. (@gaearon in #15180)findDOMNode
for components wrapped in<Suspense>
. (@acdlite in #15312)!important
style. (@acdlite in #15861 and #15882)React DOM Server
React Test Utilities and Test Renderer
act(async () => ...)
for testing asynchronous state updates. (@threepointone in #14853)act
from different renderers. (@threepointone in #16039 and #16042)act()
call. (@threepointone in #15763 and #16041)act
from the wrong renderer. (@threepointone in #15756)Artifacts
• react: https://unpkg.com/[email protected]/umd/
• react-art: https://unpkg.com/[email protected]/umd/
• react-dom: https://unpkg.com/[email protected]/umd/
• react-is: https://unpkg.com/[email protected]/umd/
• react-test-renderer: https://unpkg.com/[email protected]/umd/
• scheduler: https://unpkg.com/[email protected]/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 🌴
The text was updated successfully, but these errors were encountered: