Update react-native to the latest version 🚀 #912
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
|
The changelog should show up here, eventually: https://github.com/facebook/react-native/releases/tag/v0.43.0 |
shallow-compare is at alpha.3 because that's the most recent published version.
hawkrives
force-pushed
the
greenkeeper/react-native-0.43.0
branch
from
3e5ceca
to
1fc679d
Compare
Version 0.43.1 just got published.Update to this version instead 🚀 Release NotesMarch 2017Breaking changesCorrect value of Dimensions.get('screen').fontScaleOn Android, the following properties now return a different number:
This is a breaking change to anyone who was using these properties because the meaning of these properties has now changed. These properties used to return a value representing font scale times density ( Only call batchDidComplete when there were actually native calls dispatchedThis is breaking because it affects the contract for onBatchComplete, but modules really shouldn't (and probably aren't) depending on it being called without any actual native module method calls having happened. AndroidBugfixes
New features and enhancements
iOSBugfixes
New features and enhancements
GeneralBugfixes
New features and enhacements
|
|
According to facebook/react-native#13291 (comment), react@16-alpha.6 is stable enough for use. I'll see what I can do about Enzyme... but I might still prefer to skip 0.43 and wait for 0.44, so react@16 can be officially released. |
Version 0.43.2 just got published. |
Version 0.43.3 just got published. |
|
I'm closing this to wait for React 16 to be officially released. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 0.43.0 of react-native just got published.
Branch: https://github.com/StoDevX/AAO-React-Native/tree/greenkeeper%2Freact-native-0.43.0
The version 0.43.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-native.
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 and of course you may always ask my humans.
Your Greenkeeper Bot 🌴