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.
if (project !== 'react') {
        const peerVersion = json.peerDependencies.react.replace('^', '');
        
        
        if (semver.major(version) !== semver.major(peerVersion)) {
          json.peerDependencies.react = `^${semver.major(version)}.0.0`;
        }
      }
      await writeJson(path, json, {spaces: 2});
    };
    await Promise.all(projects.map(updateProjectPackage));
    
    await exec('yarn version-check', {cwd});
    await execUnlessDry(
      `git commit -am "Updating package versions for release ${version}"`,
      {cwd, dry}
    );
  } catch (error) {
    throw Error(
      chalk`
      Failed while updating package versions
      {white ${error.message}}
    `
    );
  }
};
module.exports = async params => {
  return logPromise(update(params), 'Updating package versions');
};