-
Notifications
You must be signed in to change notification settings - Fork 1
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 🚨 #153
Comments
After pinning to 16.5.0 your tests are passing again. Downgrade this dependency 📌. |
Your tests are still failing with these versions. Compare changes Release Notes for v16.5.2React DOM
Schedule (Experimental) |
Your tests are still failing with these versions. Compare changes |
Your tests are still failing with these versions. Compare changes Release Notes for v16.6.116.6.1 (November 6, 2018)React DOM
Scheduler (Experimental) |
Your tests are still failing with these versions. Compare changes |
Your tests are still failing with these versions. Compare changes |
Your tests are still failing with these versions. Compare changes Release Notes for v16.7.0React DOM
Scheduler (Experimental) |
Your tests are still failing with these versions. Compare changes |
Your tests are still failing with these versions. Compare changes |
Your tests are still failing with these versions. Compare changes |
Your tests are still failing with these versions. Compare changes |
Your tests are still failing with these versions. Compare changes Release Notes for v16.8.616.8.6 (March 27, 2019)React DOM
Artifacts
|
Your tests are still failing with these versions. Compare changes Release Notes for 16.9.0 (August 8, 2019)React
React DOM
React DOM ServerReact Test Utilities and Test Renderer
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.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 monorepoundefined
🚨 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 v16.5.1
16.5.1 (September 13, 2018)
React
React.forwardRef
receives an unexpected number of arguments. (@andresroberto in #13636)React DOM
isReactComponent
. (@gaearon in #13608)react-dom/profiling
withschedule/tracking
. (@bvaughn in #13605)ForwardRef
component defines adisplayName
, use it in warnings. (@probablyup in #13615)Schedule (Experimental)
schedule/tracking-profiling
. (@bvaughn in #13605)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: