af08b5cbca
* Build script creates git tag * Build script post instructions print better relative paths * Pre-release (<1.0) version numbers also include pre-release suffix (eg '-beta.0') * Post-NPM-publish step properly handles minor rev comparison check * Release script also updates @next tag when publishing @latest * Fixed a typo. Improved inline comment. |
||
|---|---|---|
| .. | ||
| 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).