Update Changelog for v15.5.1-15.5.4 #9537
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,30 @@ | ||
| ## 15.5.4 (April 11, 2017) | ||
|
|
||
| ### React Test Renderer | ||
|
|
||
| * Fix compatibility with Enzyme by exposing `batchedUpdates` on shallow renderer. [See #9382](https://github.com/facebook/react/commit/69933e25c37cf5453a9ef132177241203ee8d2fd). | ||
|
There was a problem hiding this comment. Assuming we'll fix up the link format here too to match others. There was a problem hiding this comment. Thanks - missed that one. Will fix. |
||
|
|
||
|
|
||
| ## 15.5.3 (April 7, 2017) | ||
|
There was a problem hiding this comment. AFAIK versions before 15.5.4 are using prop-types < 15.5.7 in the UMD, thus having the same critical issue. So we should make it clear all of them are effectively deprecated, and people should skip 15.5.0 to 15.5.3, and use at least 15.5.4. There was a problem hiding this comment. Great - for now I'll add the same disclaimer from the 'prop-types' repo. Was also thinking of adding the 'yanked' annotation but since that would be a new convention will propose it in a follow-up PR. |
||
|
|
||
| ### React Addons | ||
|
|
||
| * Fix react-addons-create-fragment package to export correct thing. ([@gaearon](https://github.com/gaearon) in [#9385](https://github.com/facebook/react/pull/9383)) | ||
|
There was a problem hiding this comment. Nit: lets use backticks for package names. We don't use them for proper names though (e.g. we either write React DOM or There was a problem hiding this comment. Ah - good to know. Fixing now. :) |
||
|
|
||
| ## 15.5.2 (April 7, 2017) | ||
|
|
||
| ### React Addons | ||
|
|
||
| * Fix the production single-file builds to not include the development code ([@gaearon](https://github.com/gaearon) in [#9385](https://github.com/facebook/react/pull/9383)) | ||
| * Apply better minification to production single-file builds ([@gaearon](https://github.com/gaearon) in [#9385](https://github.com/facebook/react/pull/9383)) | ||
| * Add missing and remove unnecessary dependencies to packages ([@gaearon](https://github.com/gaearon) in [#9385](https://github.com/facebook/react/pull/9383)) | ||
|
|
||
| ## 15.5.1 (April 7, 2017) | ||
|
|
||
| ### React | ||
|
|
||
| * Fix erroneous PropTypes access warning ([@acdlite](https://github.com/acdlite) in ([ec97ebb](https://github.com/facebook/react/commit/ec97ebbe7f15b58ae2f1323df39d06f119873344)) | ||
|
|
||
| ## 15.5.0 (April 7, 2017) | ||
|
|
||
| ### React | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here, we try to separate React, React DOM, and React Test Renderer changes.
Can we make it clearer which package each change corresponds to?
I also think it might be simpler to roll addon updates right into this list, and summarize them as React Addons bullet point list for each version instead of giving each addon a section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure - maybe that will be less confusing after all. Although then it's a bit tricky to map the add-on version to the React version. I guess I would annotate them in the section where React was using that version of the add-on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also will update all these to use the '[@author] in [#PR/commit]' format.