OSSForks/react
1
0
Fork 0
mirror of https://github.com/zebrajr/react.git synced 2025-12-07 12:20:38 +01:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity
1e97a71a82
react/scripts/release
History
Floris Doolaard 1e97a71a82 Fix documentation of the release process (#12337) 
* Adusted grammar in release script readme.

* Adjusts title and explanation about the release process.
2018-04-16 15:45:13 +01: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
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
README.md Fix documentation of the release process (#12337) 2018-04-16 15:45:13 +01: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 Scripts

At a high-level, the release process uses two scripts: build and publish.

  1. The build script does the heavy lifting (e.g., 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, e.g.:

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