Add a note about expiring OTP codes

scripts/release/README.md

@@ -38,6 +38,8 @@ Once the canary has been checked out and tested locally, you're ready to publish
 scripts/release/publish.js --tags next
 ```
 
+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.
+
 <sup>1: You can omit the `build` param if you just want to release the latest commit as a canary.</sup>
 
 ## Publishing an Experimental Canary
@@ -52,6 +54,8 @@ When publishing an experimental canary, use the `experimental` tag:
 scripts/release/publish.js --tags experimental
 ```
 
+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.
+
 ## Publishing a Stable Release
 
 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:
 scripts/release/publish.js --tags next latest
 ```
 
+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.
+
 After successfully publishing the release, follow the on-screen instructions to ensure that all of the appropriate post-release steps are executed.
 
 <sup>1: You can omit the `version` param if you just want to promote the latest canary to stable.</sup>