Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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

Open
greenkeeper bot opened this issue Jun 13, 2018 · 12 comments
Open

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

greenkeeper bot opened this issue Jun 13, 2018 · 12 comments
Labels
greenkeeper

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jun 13, 2018

Version 16.4.1 of react was just published.

Branch Build failing 🚨
Dependency react
Current Version 16.4.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

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

16.4.1 (June 13, 2018)

React

  • You can now assign propTypes to components returned by React.ForwardRef. (@bvaughn in #12911)

React DOM

  • Fix a crash when the input type changes from some other types to text. (@spirosikmd in #12135)
  • Fix a crash in IE11 when restoring focus to an SVG element. (@ThaddeusJiang in #12996)
  • Fix a range input not updating in some cases. (@Illu in #12939)
  • Fix input validation triggering unnecessarily in Firefox. (@nhunzaker in #12925)
  • Fix an incorrect event.target value for the onChange event in IE9. (@nhunzaker in #12976)
  • Fix a false positive error when returning an empty <React.Fragment /> from a component. (@philipp-spiess in #12966)

React DOM Server

React Test Renderer

  • Allow multiple root children in test renderer traversal API. (@gaearon in #13017)
  • Fix getDerivedStateFromProps() in the shallow renderer to not discard the pending state. (@fatfisz in #13030)
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
Copy link
Contributor Author

greenkeeper bot commented Jun 13, 2018

After pinning to 16.4.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 1, 2018

Version 16.4.2 just got published.

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

Release Notes v16.4.2

16.4.2 (August 1, 2018)

React DOM Server

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 6, 2018

Version 16.5.0 just got published.

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

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 14, 2018

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

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)

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 19, 2018

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

Your tests are still failing with these versions. Compare changes

Release Notes for v16.5.2

React DOM

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)

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Feb 6, 2019

  • The devDependency react was updated from 16.7.0 to 16.8.0.
  • The devDependency react-dom was updated from 16.7.0 to 16.8.0.

Your tests are still failing with these versions. Compare changes

Release Notes for v16.8.0

React

  • Add Hooks — a way to use state and other React features without writing a class. (@acdlite et al. in #13968)
  • Improve the useReducer Hook lazy initialization API. (@acdlite in #14723)

React DOM

  • Bail out of rendering on identical values for useState and useReducer Hooks. (@acdlite in #14569)
  • Use Object.is algorithm for comparing useState and useReducer values. (@Jessidhia in #14752)
  • Don’t compare the first argument passed to useEffect/useMemo/useCallback Hooks. (@acdlite in #14594)
  • Support synchronous thenables passed to React.lazy(). (@gaearon in #14626)
  • Render components with Hooks twice in Strict Mode (DEV-only) to match class behavior. (@gaearon in #14654)
  • Warn about mismatching Hook order in development. (@threepointone in #14585 and @acdlite in #14591)
  • Effect clean-up functions must return either undefined or a function. All other values, including null, are not allowed. @acdlite in #14119

React Test Renderer and Test Utils

  • Support Hooks in the shallow renderer. (@trueadm in #14567)
  • Fix wrong state in shouldComponentUpdate in the presence of getDerivedStateFromProps for Shallow Renderer. (@chenesan in #14613)
  • Add ReactTestRenderer.act() and ReactTestUtils.act() for batching updates so that tests more closely match real behavior. (@threepointone in #14744)

ESLint Plugin: React Hooks

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Feb 6, 2019

  • The devDependency react was updated from 16.8.0 to 16.8.1.
  • The devDependency react-dom was updated from 16.8.0 to 16.8.1.

Your tests are still failing with these versions. Compare changes

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Feb 14, 2019

  • The devDependency react was updated from 16.8.1 to 16.8.2.
  • The devDependency react-dom was updated from 16.8.1 to 16.8.2.

Your tests are still failing with these versions. Compare changes

Release Notes for v16.8.2

16.8.2 (February 14, 2019)

React DOM

  • Fix ReactDOM.render being ignored inside useEffect. (@gaearon in #14799)
  • Fix a crash when unmounting empty portals. (@gaearon in #14820)
  • Fix useImperativeHandle to work correctly when no deps are specified. (@gaearon in #14801)
  • Fix crossOrigin attribute to work in SVG image elements. (@aweary in #14832)
  • Fix a false positive warning when using Suspense with Hooks. (@gaearon in #14821)

React Test Utils and React Test Renderer

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Feb 21, 2019

  • The devDependency react was updated from 16.8.2 to 16.8.3.
  • The devDependency react-dom was updated from 16.8.2 to 16.8.3.

Your tests are still failing with these versions. Compare changes

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 6, 2019

  • The devDependency react was updated from 16.8.3 to 16.8.4.
  • The devDependency react-dom was updated from 16.8.3 to 16.8.4.

Your tests are still failing with these versions. Compare changes

Release Notes for v16.8.4

16.8.4 (March 5, 2019)

React DOM and other renderers

  • Fix a bug where DevTools caused a runtime error when inspecting a component that used a useContext hook. (@bvaughn in #14940)

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 22, 2019

  • The devDependency react was updated from 16.8.4 to 16.8.5.
  • The devDependency react-dom was updated from 16.8.4 to 16.8.5.

Your tests are still failing with these versions. Compare changes

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 30, 2019

  • The devDependency react was updated from 16.8.5 to 16.8.6.
  • The devDependency react-dom was updated from 16.8.5 to 16.8.6.

Your tests are still failing with these versions. Compare changes

Release Notes for v16.8.6

16.8.6 (March 27, 2019)

React DOM

Artifacts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
greenkeeper
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants