Files
react/scripts/release
Andrew Clark 1fd205ad2d Additional release script options for publishing canary versions (#12219)
* Additional release script options for publishing canary versions

- `branch` specifies a branch other than master
- `local` skips pulling from the remote branch and checking CircleCI
- `tag` specifies an npm dist tag other than `latest` or `next`

We may add a higher-level `canary` option in the future.

* Address Brian's feedback:

- Updated description of `local` option
- Throws if the `latest` tag is specified for a prerelease version
2018-02-13 11:44:27 -08:00
..
2018-02-04 08:54:42 -08:00
2017-10-16 15:01:14 -07:00
2017-11-09 16:29:51 +00:00
2017-10-16 15:01:14 -07:00

React Release Script

At a high-level, the release script runs in 2 passes: build and publish.

  1. The build script does the heavy lifting (eg checking CI, running automated tests, building Rollup bundles) and then prints instructions for manual verification.
  2. The publish script then publishes the built artifacts to NPM and pushes to GitHub.

Run either script without parameters to see its usage, eg:

./scripts/release/build.js
./scripts/release/publish.js

Each script will guide the release engineer through any necessary steps (including environment setup and manual testing steps).