From f20453baee8c1cbe07e8f864a7c13be57537e865 Mon Sep 17 00:00:00 2001 From: Martin Konicek Date: Fri, 22 Jan 2016 18:55:35 +0000 Subject: [PATCH] Update Releases.md --- Releases.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Releases.md b/Releases.md index 80a15f9a78dce4..324d9edd2259b1 100644 --- a/Releases.md +++ b/Releases.md @@ -47,6 +47,8 @@ To go through all the commits that went into a release, one way is to use the gi Skip this for now, ping @mkonicek on messenger and he'll handle it. Docs [here](https://github.com/facebook/react-native/blob/master/Releases-publish.md). +IMPORTANT: `npm publish` will automatically set the latest tag. **When doing an RC release**, run `npm publish --tag next` - this way people need to opt in to get the RC release. + ## Track bug reports from the community during the following two weeks and make sure they get fixed A good way to do this is to create a github issue and post about it so people can report bugs: https://github.com/facebook/react-native/issues/5201