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 checkUncommittedChanges(params);
    await checkNpmPermissions(params);
    await updateGit(params);
    await checkCircleCiStatus(params);
    await installYarnDependencies(params);
    await checkPackageDependencies(params);
    await updateYarnDependencies(params);
    await runAutomatedTests(params);
    await updatePackageVersions(params);
    await buildArtifacts(params);
    await printPostBuildSummary(params);
  } catch (error) {
    logUpdate.clear();
    const message = error.message.trim().replace(/\n +/g, '\n');
    const stack = error.stack.replace(error.message, '');
    console.log(
      `${chalk.bgRed.white(' ERROR ')} ${chalk.red(message)}\n\n${chalk.gray(stack)}`
    );
    process.exit(1);
  }
};
exec('yarn install', {cwd: __dirname}, (error, stdout, stderr) => {
  if (error) {
    console.error(error);
    process.exit(1);
  } else {
    run();
  }
});