maxjhandsome
/
react
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
react/scripts/release
History
Brian Vaughn c2c3c0cc36
Fix build script to handle react-is (no peer deps) (#12471) 		2018-03-27 19:19:34 -07:00
..
build-commands Fix build script to handle react-is (no peer deps) (#12471) 2018-03-27 19:19:34 -07:00
publish-commands Additional release script options for publishing canary versions (#12219) 2018-02-13 11:44:27 -08:00
README.md Tweaked wording of release script README 2017-10-16 15:02:41 -07:00
build.js Pre-release version fix (#12148) 2018-02-04 08:54:42 -08:00
config.js Additional release script options for publishing canary versions (#12219) 2018-02-13 11:44:27 -08:00
package.json Release script (#11223) 2017-10-16 15:01:14 -07:00
publish.js Release script tweaks (#11504) 2017-11-09 16:29:51 +00:00
utils.js Add bundle linting and tests to the release script (#11662) 2017-11-26 16:47:20 +00:00
yarn.lock Release script (#11223) 2017-10-16 15:01:14 -07:00

README.md

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).