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.

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

chore(deps): update dependency react-test-renderer to v16 #2400

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 27, 2017

This Pull Request updates dependency react-test-renderer from v15.6.1 to v16.2.0

Note: This PR was created on a configured schedule ("every weekend" in timezone Europe/Paris) and will not receive updates outside those times.

Release Notes

v15.6.2

All Packages
  • Switch from BSD + Patents to MIT license
React DOM
  • Fix a bug where modifying document.documentMode would trigger IE detection in other browsers, breaking change events. ([@​aweary] in #​10032)
  • CSS Columns are treated as unitless numbers. ([@​aweary] in #​10115)
  • Fix bug in QtWebKit when wrapping synthetic events in proxies. ([@​walrusfruitcake] in #​10115)
  • Prevent event handlers from receiving extra argument in development. ([@​aweary] in #​10115)
  • Fix cases where onChange would not fire with defaultChecked on radio inputs. ([@​jquense] in #​10156)
  • Add support for controlList attribute to DOM property whitelist ([@​nhunzaker] in #​9940)
  • Fix a bug where creating an element with a ref in a constructor did not throw an error in development. ([@​iansu] in #​10025)

v16.0.0

New JS Environment Requirements
New Features
  • Components can now return arrays and strings from render. (Docs coming soon!)
  • Improved error handling with introduction of "error boundaries". Error boundaries are React components that catch JavaScript errors anywhere in their child component tree, log those errors, and display a fallback UI instead of the component tree that crashed.
  • First-class support for declaratively rendering a subtree into another DOM node with ReactDOM.createPortal(). (Docs coming soon!)
  • Streaming mode for server side rendering is enabled with ReactDOMServer.renderToNodeStream() and ReactDOMServer.renderToStaticNodeStream(). ([@​aickin] in #​10425, #​10044, #​10039, #​10024, #​9264, and others.)
  • React DOM now allows passing non-standard attributes. ([@​nhunzaker] in #​10385, 10564, #​10495 and others)
Breaking Changes
  • There are several changes to the behavior of scheduling and lifecycle methods:
    • ReactDOM.render() and ReactDOM.unstable_renderIntoContainer() now return null if called from inside a lifecycle method.
      • To work around this, you can either use the new portal API or refs.
    • Minor changes to setState behavior:
      • Calling setState with null no longer triggers an update. This allows you to decide in an updater function if you want to re-render.
      • Calling setState directly in render always causes an update. This was not previously the case. Regardless, you should not be calling setState from render.
      • setState callback (second argument) now fires immediately after componentDidMount / componentDidUpdate instead of after all components have rendered.
    • When replacing <A /> with <B />, B.componentWillMount now always happens before A.componentWillUnmount. Previously, A.componentWillUnmount could fire first in some cases.
    • Previously, changing the ref to a component would always detach the ref before that component's render is called. Now, we change the ref later, when applying the changes to the DOM.
    • It is not safe to re-render into a container that was modified by something other than React. This worked previously in some cases but was never supported. We now emit a warning in this case. Instead you should clean up your component trees using ReactDOM.unmountComponentAtNode. See this example.
    • componentDidUpdate lifecycle no longer receives prevContext param. ([@​bvaughn] in #​8631)
    • Non-unique keys may now cause children to be duplicated and/or omitted. Using non-unique keys is not (and has never been) supported, but previously it was a hard error.
    • Shallow renderer no longer calls componentDidUpdate() because DOM refs are not available. This also makes it consistent with componentDidMount() (which does not get called in previous versions either).
    • Shallow renderer does not implement unstable_batchedUpdates() anymore.
    • ReactDOM.unstable_batchedUpdates now only takes one extra argument after the callback.
  • The names and paths to the single-file browser builds have changed to emphasize the difference between development and production builds. For example:
    • react/dist/react.jsreact/umd/react.development.js
    • react/dist/react.min.jsreact/umd/react.production.min.js
    • react-dom/dist/react-dom.jsreact-dom/umd/react-dom.development.js
    • react-dom/dist/react-dom.min.jsreact-dom/umd/react-dom.production.min.js
  • The server renderer has been completely rewritten, with some improvements:
    • Server rendering does not use markup validation anymore, and instead tries its best to attach to existing DOM, warning about inconsistencies. It also doesn't use comments for empty components and data-reactid attributes on each node anymore.
    • Hydrating a server rendered container now has an explicit API. Use ReactDOM.hydrate instead of ReactDOM.render if you're reviving server rendered HTML. Keep using ReactDOM.render if you're just doing client-side rendering.
  • When "unknown" props are passed to DOM components, for valid values, React will now render them in the DOM. See this post for more details. ([@​nhunzaker] in #​10385, 10564, #​10495 and others)
  • Errors in the render and lifecycle methods now unmount the component tree by default. To prevent this, add error boundaries to the appropriate places in the UI.
Removed Deprecations
  • There is no react-with-addons.js build anymore. All compatible addons are published separately on npm, and have single-file browser versions if you need them.
  • The deprecations introduced in 15.x have been removed from the core package. React.createClass is now available as create-react-class, React.PropTypes as prop-types, React.DOM as react-dom-factories, react-addons-test-utils as react-dom/test-utils, and shallow renderer as react-test-renderer/shallow. See 15.5.0 and 15.6.0 blog posts for instructions on migrating code and automated codemods.

v16.1.0

Discontinuing Bower Releases

Starting with 16.1.0, we will no longer be publishing new releases on Bower. You can continue using Bower for old releases, or point your Bower configs to the React UMD builds hosted on unpkg that mirror npm releases and will continue to be updated.

All Packages
  • Fix an accidental extra global variable in the UMD builds. ([@​gaearon] in #​10935)
React
  • Add support for portals in React.Children utilities. ([@​MatteoVH] in #​11378)
  • Warn when a class has a render method but doesn't extend a known base class. ([@​sw-yx] in #​11168)
  • Improve the warning when accidentally returning an object from constructor. ([@​deanbrophy] in #​11395)
React DOM
  • Allow on as a custom attribute for AMP. ([@​nuc] in #​11153)
  • Fix onMouseEnter and onMouseLeave firing on wrong elements. ([@​gaearon] in #​11164)
  • Fix null showing up in a warning instead of the component stack. ([@​gaearon] in #​10915)
  • Fix IE11 crash in development mode. ([@​leidegre] in #​10921)
  • Fix tabIndex not getting applied to SVG elements. ([@​gaearon] in #​11034)
  • Fix SVG children not getting cleaned up on dangerouslySetInnerHTML in IE. ([@​OriR] in #​11108)
  • Fix false positive text mismatch warning caused by newline normalization. ([@​gaearon] in #​11119)
  • Fix form.reset() to respect defaultValue on uncontrolled <select>. ([@​aweary] in #​11057)
  • Fix <textarea> placeholder not rendering on IE11. ([@​gaearon] in #​11177)
  • Fix a crash rendering into shadow root. ([@​gaearon] in #​11037)
  • Fix false positive warning about hydrating mixed case SVG tags. ([@​gaearon] in #​11174)
  • Suppress the new unknown tag warning for <dialog> element. ([@​gaearon] in #​11035)
  • Warn when defining a non-existent componentDidReceiveProps method. ([@​iamtommcc] in #​11479)
  • Warn about function child no more than once. ([@​andreysaleba] in #​11120)
  • Warn about nested updates no more than once. ([@​anushreesubramani] in #​11113)
  • Deduplicate other warnings about updates. ([@​anushreesubramani] in #​11216)
  • Include component stack into the warning about contentEditable and children. ([@​Ethan-Arrowood] in #​11208)
  • Improve the warning about booleans passed to event handlers. ([@​NicBonetto] in #​11308)
  • Improve the warning when a multiple select gets null value. ([@​Hendeca] in #​11141)
  • Move link in the warning message to avoid redirect. ([@​marciovicente] in #​11400)
  • Add a way to suppress the React DevTools installation prompt. ([@​gaearon] in #​11448)
  • Remove unused code. ([@​gaearon] in #​10802, #​10803)
React DOM Server
  • Add a new suppressHydrationWarning attribute for intentional client/server text mismatches. ([@​sebmarkbage] in #​11126)
  • Fix markup generation when components return strings. ([@​gaearon] in #​11109)
  • Fix obscure error message when passing an invalid style value. ([@​iamdustan] in #​11173)
  • Include the autoFocus attribute into SSR markup. ([@​gaearon] in #​11192)
  • Include the component stack into more warnings. ([@​gaearon] in #​11284)
React Test Renderer and Test Utils
  • Fix multiple setState() calls in componentWillMount() in shallow renderer. ([@​Hypnosphi] in #​11167)
  • Fix shallow renderer to ignore shouldComponentUpdate() after forceUpdate(). ([@​d4rky-pl] in #​11239 and #​11439)
  • Handle forceUpdate() and React.PureComponent correctly. ([@​koba04] in #​11440)
  • Add back support for running in production mode. ([@​gaearon] in #​11112)
  • Add a missing package.json dependency. ([@​gaearon] in #​11340)
React ART
  • Add a missing package.json dependency. ([@​gaearon] in #​11341)
  • Expose react-art/Circle, react-art/Rectangle, and react-art/Wedge. ([@​gaearon] in #​11343)
React Reconciler (Experimental)
  • First release of the new experimental package for creating custom renderers. ([@​iamdustan] in #​10758)
  • Add support for React DevTools. ([@​gaearon] in #​11463)
React Call Return (Experimental)

v16.1.1

React
  • Improve the warning about undefined component type. ([@​selbekk] in #​11505)
React DOM
  • Support string values for the capture attribute. ([@​maxschmeling] in #​11424)
React DOM Server
  • Don't freeze the ReactDOMServer public API. ([@​travi] in #​11531)
  • Don't emit autoFocus={false} attribute on the server. ([@​gaearon] in #​11543)
React Reconciler
  • Change the hydration API for better Flow typing. ([@​sebmarkbage] in #​11493)

v16.2.0

React
  • Add Fragment as named export to React. ([@​clemmy] in #​10783)
  • Support experimental Call/Return types in React.Children utilities. ([@​MatteoVH] in #​11422)
React DOM
  • Fix radio buttons not getting checked when using multiple lists of radios. ([@​landvibe] in #​11227)
  • Fix radio buttons not receiving the onChange event in some cases. ([@​jquense] in #​11028)
React Test Renderer
  • Fix setState() callback firing too early when called from componentWillMount. ([@​accordeiro] in #​11507)
React Reconciler
  • Expose react-reconciler/reflection with utilities useful to custom renderers. ([@​rivenhk] in #​11683)
Internal Changes
  • Many tests were rewritten against the public API. Big thanks to everyone who contributed!


This PR has been generated by Renovate Bot.

@algobot
Copy link
Contributor

algobot commented Sep 27, 2017

Deploy preview for algolia-instantsearch ready!

Built with commit 2b772a7

https://deploy-preview-2400--algolia-instantsearch.netlify.com

@renovate renovate bot force-pushed the renovate/react-monorepo branch 13 times, most recently from 9aa4fe8 to 4cf3195 Compare October 9, 2017 15:40
@renovate renovate bot force-pushed the renovate/react-monorepo branch 8 times, most recently from 4bdf2fb to 5965724 Compare October 17, 2017 09:33
@renovate renovate bot force-pushed the renovate/react-monorepo branch 8 times, most recently from 75b49a9 to 2c42db9 Compare October 22, 2017 12:29
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 4445cb7 to 8cb30f1 Compare January 4, 2018 16:28
@renovate renovate bot force-pushed the renovate/react-monorepo branch 4 times, most recently from b83ee10 to 55895a2 Compare January 28, 2018 10:15
@renovate renovate bot force-pushed the renovate/react-monorepo branch 7 times, most recently from ee1e88a to 2bcba4d Compare February 5, 2018 14:25
@renovate renovate bot force-pushed the renovate/react-monorepo branch 7 times, most recently from 9a34283 to 2127517 Compare February 11, 2018 22:01
@renovate renovate bot force-pushed the renovate/react-monorepo branch 5 times, most recently from 3b70ba0 to 4341b6d Compare February 15, 2018 10:51
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 4341b6d to 2b772a7 Compare February 15, 2018 14:16
@bobylito
Copy link
Contributor

Preact-compat doesn't implement the newest react API, therefore we won't be able to upgrade this one for the moment.

@bobylito bobylito closed this Feb 15, 2018
@renovate
Copy link
Contributor Author

renovate bot commented Feb 15, 2018

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 16.x releases. However, if you upgrade to 16.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

@renovate renovate bot deleted the renovate/react-monorepo branch February 15, 2018 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants