mirror of
https://github.com/zebrajr/react.git
synced 2026-01-15 12:15:22 +00:00
d9e0485c84
## Summary I ran into some two factor certification issue and had to resume the publish script. However, this time if I confirmed the published package, it will still try to publish the same version and fail. This is not expected, and it blocks me from publishing the rest of the packages. ## How did you test this change? I re-run the publish script after the change and successfully publish the rest of the packages. ``` ? Have you run the build-and-test script? Yes ✓ Checking NPM permissions for ryancat. 881 ms ? Please provide an NPM two-factor auth token: 278924 react-devtools version 4.27.2 has already been published. ? Is this expected (will skip react-devtools@4.27.2)? Yes react-devtools-core version 4.27.2 has already been published. ? Is this expected (will skip react-devtools-core@4.27.2)? Yes ✓ Publishing package react-devtools-inline 23.1 secs You are now ready to publish the extension to Chrome, Edge, and Firefox: https://fburl.com/publish-react-devtools-extensions When publishing to Firefox, remember the following: Build id: 625690 Git archive: ****** ```
Releasing DevTools
To release DevTools, do the following steps (in order):
Each of the scripts can be run with a --dry flag to test without committing or publishing any changes.
Prepare a release
To increment version numbers and update the CHANGELOG, run the prepare-release script:
./prepare-release.js
You'll need to follow the instructions at the end of the script to push the committed changes to the main fork on GitHub.
Build and test a release
To build and test a release, run the build-and-test script:
./build-and-test.js
Publish a release
To publish a release to NPM, run the publish-release script:
./publish-release.js
You'll need to follow the instructions at the end of the script to upload the extension to Chrome, Edge, and Firefox stores.