OSSForks/react
1
0
Fork 0
mirror of https://github.com/zebrajr/react.git synced 2025-12-07 00:20:28 +01:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity
is-renderable
react/scripts/release
History
Dan Abramov aeda7b745d
Remove fbjs dependency (#13069) 
* Inline fbjs/lib/invariant

* Inline fbjs/lib/warning

* Remove remaining usage of fbjs in packages/*.js

* Fix lint

* Remove fbjs from dependencies

* Protect against accidental fbjs imports

* Fix broken test mocks

* Allow transitive deps on fbjs/ for UMD bundles

* Remove fbjs from release script
2018-06-19 16:03:45 +01:00
..
build-commands Separate yarn flow and yarn flow-ci (#12841) 2018-05-17 14:29:37 +01:00
publish-commands Release script prompts for NPM 2FA code (#12908) 2018-05-29 12:50:04 -07:00
build.js Release script prompts for NPM 2FA code (#12908) 2018-05-29 12:50:04 -07:00
config.js Remove fbjs dependency (#13069) 2018-06-19 16:03:45 +01:00
package.json Release script prompts for NPM 2FA code (#12908) 2018-05-29 12:50:04 -07:00
publish.js Release script prompts for NPM 2FA code (#12908) 2018-05-29 12:50:04 -07: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 prompts for NPM 2FA code (#12908) 2018-05-29 12:50:04 -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).