The list of releases with notes can be found at: https://github.com/facebook/react-native/releases
Future releases:
- 0.17 branch cut, 0.17.0-rc - beginning of week of Dec 7
- 0.17.0 - Dec 17
- (Holiday break)
- 0.18 branch cut, 0.18.0-rc - week of Jan 4
- 0.18.0 - Jan 18
- 0.19 branch cut, 0.19.0-rc - week of Jan 18
- 0.19.0 - Feb 1
- 0.20 branch cut, 0.19.0-rc - week of Feb 1
- 0.20.0 - Feb 15
- ...
- A lot of these steps could be done by a script
- We could simplify the process quite a bit by publishing the Android binaries to npm. This will increase the size of the npm package by about 3.3MB. To do that: after
installArchives
, move the binaries to somewhere wherenpm publish
will pick them up. Then, change thebuild.gradle
file(s) of your generated app so that Gradle will pick up the binaries fromnode_modules
. This will likely also fix issues with incompatible versions of JS and Android binaries (e.g. #4488).
Set up Sinopia: https://github.com/facebook/react-native/tree/master/react-native-cli
To cut a release branch and check that everything works, you'll need Mac OS with the Android dev environment set up.
Run:
cd react-native
./scripts/release.sh 0.19 # Replace 0.19 with the version you're cutting the branch for :)
Make absolutely sure basic iOS and Android workflow works on master, see the instructions printed by release.sh
.
- Check git history, the last commit should be "[0.19-rc] Bump version numbers" (with the correct version)
git push origin 0.version_you_are_releasing-stable
Skip this for now, ping @mkonicek on messenger and he'll handle it. Docs here.
A good way to do this is to create a github issue and post about it so people can report bugs: facebook#5201