dillon1000/react
Commit
Browse files Bypass packages that are already published when confirmed by users (#26141)
## 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 [email protected])? Yes react-devtools-core version 4.27.2 has already been published. ? Is this expected (will skip [email protected])? 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: ****** ```
Changed paths1 file
First-parent comparisonscripts/devtools/publish-release.js ModifiedPatch
Files changed
Rendering syntax-highlighted changes…