Add a note about expiring OTP codes
Dan Abramov committed
Jan 29, 2020 at 16:31 UTC
241c4467eef7c2a8858c96d5dfe4e8ef84c47bad
1 file changed
+6
scripts/release/README.md
+6
@@ -38,6 +38,8 @@ Once the canary has been checked out and tested locally, you're ready to publish
38
scripts/release/publish.js --tags next
39
```
40
41
+If the OTP code expires while publishing, re-run this command and answer "y" to the questions about whether it was expected for already published packages.
42
+
43
<sup>1: You can omit the `build` param if you just want to release the latest commit as a canary.</sup>
44
45
## Publishing an Experimental Canary
@@ -52,6 +54,8 @@ When publishing an experimental canary, use the `experimental` tag:
54
scripts/release/publish.js --tags experimental
55
```
56
57
+If the OTP code expires while publishing, re-run this command and answer "y" to the questions about whether it was expected for already published packages.
58
+
59
## Publishing a Stable Release
60
61
Stable releases should always be created from a previously-released canary. This encourages better testing of the actual release artifacts and reduces the chance of unintended changes accidentally being included in a stable release.
@@ -70,6 +74,8 @@ Once this step is complete, you're ready to publish the release:
74
scripts/release/publish.js --tags next latest
75
```
76
77
+If the OTP code expires while publishing, re-run this command and answer "y" to the questions about whether it was expected for already published packages.
78
+
79
After successfully publishing the release, follow the on-screen instructions to ensure that all of the appropriate post-release steps are executed.
80
81
<sup>1: You can omit the `version` param if you just want to promote the latest canary to stable.</sup>