[compiler] Fix outdated comment in scripts/release
ghstack-source-id: a37c6faa8b6d0fa443b5a3cb2f0d8398f8e7588c Pull Request resolved: https://github.com/facebook/react/pull/29800
Lauren Tan committed
Jun 7, 2024 at 11:46 UTC
0a5e0b0c2e496f335136c34663e8763cfa160b82
1 file changed
+5
-6
compiler/scripts/release/publish-manual.js
+5
-6
@@ -51,8 +51,6 @@ async function getDateStringForCommit(commit) {
51
}
52
53
/**
54
- * Please login to npm first with `npm login`. You will also need 2FA enabled to push to npm.
55
- *
54
* Script for publishing PUBLISHABLE_PACKAGES to npm. By default, this runs in tarball mode, meaning
55
* the script will only print out what the contents of the files included in the npm tarball would
56
* be.
@@ -60,10 +58,11 @@ async function getDateStringForCommit(commit) {
58
* Please run this first (ie `yarn npm:publish`) and double check the contents of the files that
59
* will be pushed to npm.
60
*
63
- * If it looks good, you can run `yarn npm:publish --for-real` to really publish to npm. There's a
64
- * small annoying delay before the packages are actually pushed to give you time to panic cancel. In
65
- * this mode, we will bump the version field of each package's package.json, and git commit it.
66
- * Then, the packages will be published to npm.
61
+ * If it looks good, you can run `yarn npm:publish --for-real` to really publish to npm. You must
62
+ * have 2FA enabled first and the script will prompt you to enter a 2FA code before proceeding.
63
+ * There's a small annoying delay before the packages are actually pushed to give you time to panic
64
+ * cancel. In this mode, we will bump the version field of each package's package.json, and git
65
+ * commit it. Then, the packages will be published to npm.
66
*
67
* Optionally, you can add the `--debug` flag to `yarn npm:publish --debug --for-real` to run all
68
* steps, but the final npm publish step will have the `--dry-run` flag added to it. This will make