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.
const {join} = require('path');
const semver = require('semver');
const {projects} = require('../config');
const {execUnlessDry, logPromise} = require('../utils');
const update = async ({cwd, dry, version}) => {
  try {
    
    const packagePath = join(cwd, 'package.json');
    const rootPackage = await readJson(packagePath);
    rootPackage.version = version;
    await writeJson(packagePath, rootPackage, {spaces: 2});
    
    const reactVersionPath = join(cwd, 'packages/shared/ReactVersion.js');
    const reactVersion = readFileSync(reactVersionPath, 'utf8').replace(
      /module\.exports = '[^']+';/,
      `module.exports = '${version}';`
    );
    writeFileSync(reactVersionPath, reactVersion);
    
    const updateProjectPackage = async project => {
      const path = join(cwd, 'packages', project, 'package.json');
      const json = await readJson(path);
      
      
      
      if (semver.lt(json.version, '1.0.0')) {
        json.version = `0.${semver.minor(json.version) + 1}.0`;
      } else {
        json.version = version;
      }