Today I used the [new release script](https://github.com/facebook/react/tree/master/scripts/release) for the first time to publish `16.1.0-beta`. Here are a couple of things I noticed that I want to follow-up on:

### PR #11434
- [x] Auto-install (or update) release script Yarn deps before running

### PR #11437
- [x] `publish` script should `git tag -a ${version}`. I manually tagged the `16.1.0-beta` release.
- [X] The post-build test instructions should show fully-qualified paths to prevent you from accidentally verifying the wrong build (eg the checkout the release script is running from rather than the `-p` path)
- [x] `publish-to-npm` check should handle pre-1.0 packages. (This one failed for the `0.2.0` reconciler release b'c it expected it to be 16.1.0-beta.) For that matter, it should have probably been `0.2.0-beta`
- [x] When publishing a stable release (`@latest`) also update the next release to point to it.
await execUnlessDry(`npm publish --tag ${tag}`, {cwd: path, dry});
      if (!dry) {
        const status = JSON.parse(
          await execRead(`npm info ${project} dist-tags --json`)
        );
        const remoteVersion = status[tag];
        if (remoteVersion !== version) {
          throw Error(
            chalk`Publised version {yellow.bold ${version}} for ` +
              `{bold ${project}} but NPM shows {yellow.bold ${remoteVersion}}`
          );
        }
      }
    } catch (error) {
      errors.push(error.message);
    }
  };
  await Promise.all(projects.map(publishProject));
  if (errors.length > 0) {
    throw Error(
      chalk`
      Failure publishing to NPM
      {white ${errors.join('\n')}}`
    );
  }
};
module.exports = async params => {
  return logPromise(push(params), 'Pushing to git remote');
};