react/scripts/release/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.
1. 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).
Fix documentation of the release process (#12337) * Adusted grammar in release script readme. * Adjusts title and explanation about the release process. 2018-04-16 22:45:13 +08:00			`# React Release Scripts`
Release script (#11223) * First chunk of new release script * Re-ordered build steps to combine error codes and releases * Reorganized build files; added stub publish script * First pass at publis script. Also collect and print dry-run commits/publish commands. * Deleted old react-release-manager scripts * Cleaned up release package.json * Basic README instructions * Removed unnecessary 'async' keyword from a method * Wordsmithing * Tweaked README * Renamed build -> build-commands and publish -> publish-commands to avoid conflict with .gitignore * Bump pre-release package versions differently * Prettier * Improved CircleCI API token setup instructions message * Lint fix * Typofix 2017-10-17 06:01:14 +08:00
Fix documentation of the release process (#12337) * Adusted grammar in release script readme. * Adjusts title and explanation about the release process. 2018-04-16 22:45:13 +08:00			`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.`
			`1. The publish script then publishes the built artifacts to npm and pushes to GitHub.`
Release script (#11223) * First chunk of new release script * Re-ordered build steps to combine error codes and releases * Reorganized build files; added stub publish script * First pass at publis script. Also collect and print dry-run commits/publish commands. * Deleted old react-release-manager scripts * Cleaned up release package.json * Basic README instructions * Removed unnecessary 'async' keyword from a method * Wordsmithing * Tweaked README * Renamed build -> build-commands and publish -> publish-commands to avoid conflict with .gitignore * Bump pre-release package versions differently * Prettier * Improved CircleCI API token setup instructions message * Lint fix * Typofix 2017-10-17 06:01:14 +08:00
Fix documentation of the release process (#12337) * Adusted grammar in release script readme. * Adjusts title and explanation about the release process. 2018-04-16 22:45:13 +08:00			`Run either script without parameters to see its usage, e.g.:`
Release script (#11223) * First chunk of new release script * Re-ordered build steps to combine error codes and releases * Reorganized build files; added stub publish script * First pass at publis script. Also collect and print dry-run commits/publish commands. * Deleted old react-release-manager scripts * Cleaned up release package.json * Basic README instructions * Removed unnecessary 'async' keyword from a method * Wordsmithing * Tweaked README * Renamed build -> build-commands and publish -> publish-commands to avoid conflict with .gitignore * Bump pre-release package versions differently * Prettier * Improved CircleCI API token setup instructions message * Lint fix * Typofix 2017-10-17 06:01:14 +08:00			```
			`./scripts/release/build.js`
			`./scripts/release/publish.js`
			```

Fix documentation of the release process (#12337) * Adusted grammar in release script readme. * Adjusts title and explanation about the release process. 2018-04-16 22:45:13 +08:00			`Each script will guide the release engineer through any necessary steps (including environment setup and manual testing steps).`