1fd205ad2d
* 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 |
||
|---|---|---|
| .. | ||
| build-commands | ||
| publish-commands | ||
| README.md | ||
| build.js | ||
| config.js | ||
| package.json | ||
| publish.js | ||
| utils.js | ||
| yarn.lock | ||
README.md
React Release Script
At a high-level, the release script runs in 2 passes: build and publish.
- The build script does the heavy lifting (eg checking CI, running automated tests, building Rollup bundles) and then prints instructions for manual verification.
- 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).