greenkeeper[bot]
commented
6 years ago Version 16.1.0 just got published.
Update to this version instead 🚀
Release Notes
v16.1.016.1.0 (November 9, 2017)
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
React
- Add support for portals in
React.Childrenutilities. (@MatteoVH in #11378) - Warn when a class has a
rendermethod 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
onas a custom attribute for AMP. (@nuc in #11153) - Fix
onMouseEnterandonMouseLeavefiring on wrong elements. (@gaearon in #11164) - Fix
nullshowing up in a warning instead of the component stack. (@gaearon in #10915) - Fix IE11 crash in development mode. (@leidegre in #10921)
- Fix
tabIndexnot getting applied to SVG elements. (@gaearon in #11034) - Fix SVG children not getting cleaned up on
dangerouslySetInnerHTMLin IE. (@OriR in #11108) - Fix false positive text mismatch warning caused by newline normalization. (@gaearon in #11119)
- Fix
form.reset()to respectdefaultValueon 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
componentDidReceivePropsmethod. (@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
contentEditableandchildren. (@Ethan-Arrowood in #11208) - Improve the warning about booleans passed to event handlers. (@NicBonetto in #11308)
- Improve the warning when a multiple
selectgets nullvalue. (@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
suppressHydrationWarningattribute 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
autoFocusattribute 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 incomponentWillMount()in shallow renderer. (@Hypnosphi in #11167) - Fix shallow renderer to ignore
shouldComponentUpdate()afterforceUpdate(). (@d4rky-pl in #11239 and #11439) - Handle
forceUpdate()andReact.PureComponentcorrectly. (@koba04 in #11440) - Add back support for running in production mode. (@gaearon in #11112)
- Add a missing
package.jsondependency. (@gaearon in #11340)
React ART
- Add a missing
package.jsondependency. (@gaearon in #11341) - Expose
react-art/Circle,react-art/Rectangle, andreact-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)
- First release of the new experimental package for parent-child communication. (@gaearon in #11364)
Version 16.0.0 of react just got published.
The version 16.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of react. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: